Skip to main content

GOTOP - D16 Configuration

This page documents the public configuration context for using the GOTOP D16 bike GPS tracker with Plaspy. It focuses on the practical server values and workflow needed so the D16 can report location and events to Plaspy for live monitoring, geofence alerts, and route history playback.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol. Exact manufacturer-side setup steps for the D16 can vary by firmware version, region, hardware revision, and the configuration tool provided by GOTOP, so treat the information here as the practical Plaspy-side values and workflow guidance; always confirm device-specific controls with GOTOP documentation.

Configuration Overview​

The goal of this configuration is to prepare the D16 to communicate reliably with the Plaspy cloud so devices appear in the platform and deliver timely location and alarm events. This includes applying the Plaspy server endpoint, ensuring the device has working mobile connectivity, and validating that transmissions reach Plaspy.

  • Configure the device to report to Plaspy's shared server endpoint and same port used by all Plaspy devices.
  • Ensure the D16 has active 4G connectivity and a charged battery so it can send position updates.
  • Select the appropriate transport (UDP or TCP) if the device requires a choice.
  • Save and apply settings, then confirm the device is visible and reporting on Plaspy.
  • Validate event reporting such as geofence alerts and low battery notifications once online.

Plaspy Server Settings​

Use the following public Plaspy server settings when configuring the D16:

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support: UDP or TCP may be used on port 8888
  • Plaspy automatically detects the tracker protocol so the platform will ingest compatible packets sent to the above endpoint

Plaspy uses the same port for all supported devices and will identify the device protocol automatically when packets arrive at the endpoint.

Typical Requirements Before Setup​

  • A powered and charged GOTOP D16 device with working internal battery or vehicle power connection.
  • Active cellular connectivity for the device (the D16 uses 4G LTE connectivity as described for the model).
  • Access to the device's official configuration method or software as provided by GOTOP; this may be a vendor tool, configuration app, or configuration interface—consult GOTOP documentation.
  • The Plaspy server settings from this page (d.plaspy.com or 54.85.159.138 and port 8888) available to enter into the device configuration.
  • A way to test and validate outgoing connections from the device (watch logs, device reporting LEDs, or Plaspy device list) after applying settings.

How This Tracker Connects to Plaspy​

When the D16 is configured for Plaspy, it sends its location and status packets over cellular data to the shared Plaspy endpoint on the agreed port. Plaspy ingests those packets, interprets the device protocol automatically, and updates the map and event history for operators and riders.

  • The tracker is configured to report to the shared Plaspy server endpoint d.plaspy.com (54.85.159.138) on port 8888.
  • Packets can be sent using UDP or TCP depending on device configuration; Plaspy accepts both transports on port 8888.
  • Plaspy automatically detects the tracker protocol and maps incoming telemetry to the device record.
  • Once reporting is successful, position fixes, geofence events, and battery status become visible in Plaspy for monitoring and alerts.
  • Operators can use Plaspy dashboards to receive notifications and review route history generated by D16 reports.

Common Configuration Workflow​

  1. Access the official GOTOP configuration method or software for the D16 as provided by the manufacturer.
  2. In the device server or APN configuration, enter the Plaspy server domain d.plaspy.com or the server IP 54.85.159.138 as applicable.
  3. Set the device server port to 8888 (Plaspy uses the same port for all supported devices).
  4. Choose the transport protocol UDP or TCP if the device requires a transport selection; Plaspy accepts both on port 8888.
  5. Apply or save the configuration settings in the device or vendor tool.
  6. Restart or power cycle the D16 if the configuration process requires a reboot to apply changes.
  7. Validate that the device reports to Plaspy by confirming device appearance and recent telemetry in the Plaspy platform.

Example Configuration Commands​

The D16 manufacturer may provide multiple configuration paths (vendor configuration tools, firmware web interfaces, or over the air methods). Exact command formats and tools vary by GOTOP firmware and regional model. Because GOTOP supplies device-specific configuration interfaces, this page does not invent device commands. Consult the GOTOP configuration guide or your vendor tool for exact command syntax and examples when performing server and port changes.

Configuration Notes​

  • Firmware and hardware revisions can change the configuration interface and available options; always reference the GOTOP documentation for your device revision.
  • Plaspy accepts both UDP and TCP on port 8888. If you have a transport option, choose the one that aligns with your installer practices or network stability; Plaspy will auto-detect protocol details.
  • Use either the domain d.plaspy.com or the IP 54.85.159.138 in the device configuration; some installers prefer domain names to avoid IP changes, while others use IPs in constrained configuration tools.
  • After applying settings, allow several minutes for the device to reconnect and for Plaspy to detect the protocol and register incoming telemetry.
  • Confirm APN and cellular settings on the D16 as needed for 4G connectivity; these settings are managed on the device side and are required for data delivery to Plaspy.

Why Use Plaspy with This Configuration​

Using the GOTOP D16 with Plaspy gives bicycle fleets and individual riders straightforward live location visibility, geofence alerts, and route history in a single platform. Plaspy’s centralized ingestion and automatic protocol detection reduce configuration complexity at the platform side by accepting device traffic on a shared endpoint and port, allowing operators to focus on deployment and operations.

Learn more about Plaspy on the main website https://www.plaspy.com and verify the latest D16 device specific setup and firmware details on the manufacturer site https://www.gotop.cc/. Manufacturer configuration methods and firmware behavior can change over time, so always confirm the current device documentation for the most accurate instructions.

Tracker Configuration

Need a platform for this tracker setup

Plaspy helps you connect compatible trackers, receive device data, and centralize monitoring from one GPS tracking platform.

Learn more about Plaspy