Skip to main content

iStartek - VT100 Protocol

This page summarizes the public protocol context for integrating the iStartek VT100 vehicle GPS tracker with the Plaspy platform. It focuses on how the tracker communicates with Plaspy in general terms and what to consider when configuring devices for reliable reporting and monitoring. The information here is intended for operations, integrators, and technical users who need to understand connection and protocol implications without exposing private implementation details.

Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol once messages arrive at the server. Exact protocol behavior can vary by VT100 firmware version, hardware revision, or manufacturer configuration, so device behavior in a specific deployment can differ from general descriptions. Users should combine this guidance with the VT100 product documentation and current firmware notes from the manufacturer.

Protocol Overview​

The VT100 reporting protocol is the vehicle tracker communication method that sends GNSS location, telemetry, and event data to a remote server. In practice this means the device frames periodic position reports, event notifications (for example SOS, ignition state, or collision alerts), and occasional diagnostic or offline-uploaded records for the receiving platform to interpret and display.

  • The protocol enables the VT100 to identify itself and deliver usable GPS coordinates and status fields to Plaspy.
  • It carries telemetry such as GNSS fixes, motion events from the built in accelerometer, input/output states, and optional sensor values.
  • The tracking protocol is the link between the VT100 on the vehicle and Plaspy’s ingestion pipeline where data becomes live maps, alerts, and reports.
  • Transport-level settings determine how messages reach the Plaspy endpoint but do not change the conceptual role of the protocol as the device reporting language.
  • Protocol behavior can include periodic reporting, event-driven messages, and buffered uploads after offline periods, depending on VT100 configuration.

How Plaspy Detects the Protocol​

Plaspy receives device reports on a single, shared entry point and automatically determines the protocol used by a device based on the messages it receives. For most VT100 deployments this automatic detection means users do not need to manually select a tracker protocol inside Plaspy when the device is configured correctly to report to the Plaspy endpoint.

  • Plaspy’s public server endpoint for device reporting is d.plaspy.com and the associated server IP is 54.85.159.138.
  • The Plaspy ingestion port for all devices is 8888 and Plaspy uses the same port for every supported tracker model.
  • Devices may be configured to send data using UDP or TCP to port 8888; Plaspy accepts both transports.
  • When a VT100 sends properly addressed reports to the Plaspy endpoint, the platform attempts to identify the device protocol automatically.
  • In many cases no manual protocol selection is required in Plaspy if the VT100 is pointed to the correct server and transport.

Transport and Connection Context​

Connection settings govern how the VT100 reaches Plaspy but are distinct from the protocol semantics contained in device messages. The VT100 supports cellular GPRS for uplink and can be configured to use either UDP or TCP to send data to the tracking server. Use the following connection facts when configuring devices or validating communications.

  • Devices may point to the Plaspy domain d.plaspy.com or directly to the IP address 54.85.159.138.
  • The port used for reporting to Plaspy is 8888; this is the same port used for all devices in Plaspy.
  • The VT100 can be set to transmit over UDP or TCP on port 8888 depending on device configuration and network conditions.
  • Choose UDP for low-latency, connectionless reporting when supported by the device; choose TCP when a reliable connection-oriented transport is preferred or required by firmware.
  • Ensure the device APN and GPRS settings allow outbound traffic to the Plaspy endpoint and that any carrier firewalls permit the chosen transport to port 8888.

Protocol Compatibility Notes​

  • Firmware variations can change how the VT100 formats or times messages; verify firmware release notes for protocol-related changes before large rollouts.
  • Hardware revisions or optional modules (for example fuel sensors or RS232 adapters) may introduce additional fields or event types in reported messages.
  • Manufacturer-side configuration (SMS/GPRS commands, dual-server upload options, or offline logging behavior) can affect how and when telemetry is delivered.
  • Transport selection (UDP vs TCP) is dependent on device support and can influence delivery guarantees and server-side parsing expectations.
  • Plaspy’s automatic protocol detection reduces manual setup but accurate device addressing (d.plaspy.com or 54.85.159.138 and port 8888) is essential for detection to occur.
  • Validate compatibility by testing a sample device with Plaspy and consult VT100 official documentation for firmware specific behaviors.

Why Protocol Understanding Matters​

Understanding the VT100 communication protocol helps operators and integrators configure devices correctly, diagnose connectivity or telemetry issues, and plan maintenance or firmware update strategies. Clear protocol context shortens troubleshooting cycles and helps ensure consistent, reliable data flows into Plaspy.

  • Proper configuration of server address, transport, and APN is the first step to successful reporting.
  • Recognizing how events are reported clarifies why certain alerts or telemetry values appear in Plaspy dashboards.
  • Awareness of offline logging and forward behavior guides expectations during coverage outages and reconnection.
  • Knowledge of firmware-related protocol changes helps schedule testing and staged rollouts to avoid unexpected behavior.
  • Understanding transport tradeoffs (UDP vs TCP) helps align device settings with operational priorities for latency and reliability.

Why Use Plaspy with This Protocol​

Using the VT100 with Plaspy provides organizations with a stable path from vehicle-mounted telemetry to operational insight. The combination of VT100 hardware features—accurate GNSS, motion detection, optional sensor inputs, and rugged design—with Plaspy’s centralized ingestion and visualization enables live tracking, geofence alerts, route history, and event-driven workflows that support fleet operations and security response.

Plaspy’s shared endpoint model and automatic protocol detection simplify onboarding: point VT100 devices to d.plaspy.com or 54.85.159.138 on port 8888 using UDP or TCP, and Plaspy will attempt to interpret device reports into live telemetry. To learn more about Plaspy and platform capabilities visit https://www.plaspy.com. Please note that protocol support, firmware behavior, and device implementation details can change over time; verify the latest VT100 documentation and firmware notes on the manufacturer site https://istartek.com/ for current device specific information.

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