Skip to main content

DCT - Titan Tracker Configuration

This page documents the public configuration context for using the DCT Titan Tracker with Plaspy. It focuses on the practical server settings and a Syrus SB script example that you can use with Syrus Desk or the device management workflow to point the Titan Tracker to Plaspy for real-time tracking and event reporting.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol. Exact steps you perform on the manufacturer side can vary by firmware version, hardware revision, installation type, and vendor tools such as Syrus Desk or Pegasus Gateway. An example Syrus SB script from the manufacturer is included below to illustrate a typical configuration flow.

Configuration Overview​

The goal of configuration is to prepare the Titan Tracker to communicate reliably with Plaspy, ensure network connectivity is valid, and enable the device to report location, SOS, and event data into the Plaspy platform. This page provides the Plaspy server details you must use and a practical example script you can adapt.

  • Set the tracker to use Plaspy as the remote AVL server so position and events are delivered to the platform.
  • Configure APN and cellular parameters so the device has a working data connection before pointing to Plaspy.
  • Choose the transport (UDP or TCP) and confirm that the device saves and uses the selected port.
  • Validate the device reports to Plaspy and that events such as SOS, motion, and input reports appear in the platform.
  • Use the provided Syrus SB script example as a starting point when configuring via Syrus Desk or manufacturer tools.

Plaspy Server Settings​

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support: configure UDP or TCP on port 8888 depending on device transport selection
  • Plaspy automatically detects the tracker protocol so the same port is used for all supported devices

Typical Requirements Before Setup​

  • A fully charged Titan Tracker or stable power supply for the device during configuration.
  • An active cellular SIM with data enabled and the correct APN for your mobile operator.
  • Access to the official manufacturer configuration tools such as Syrus Desk or the Pegasus Gateway IoT Platform for OTA management.
  • The Plaspy server settings (d.plaspy.com or 54.85.159.138 and port 8888) available to enter into the device configuration.
  • Basic knowledge of the device model SKU (3G ST-1734G or 4G ST-4GM1) to confirm network compatibility and APN requirements.
  • A plan to validate device connectivity from the field and confirm visibility within Plaspy after configuration.

How This Tracker Connects to Plaspy​

When configured, the Titan Tracker sends position updates, alert events, and status information to the shared Plaspy server endpoint and port. Plaspy ingests these messages and associates them with the device record so location, SOS alerts, and motion events become visible in dashboards and notifications.

  • Tracker reports position updates to d.plaspy.com (or 54.85.159.138) on port 8888 using UDP or TCP depending on the device configuration.
  • SOS and panic activations are forwarded to Plaspy for alerting and escalation rules.
  • Motion and impact events generated by the accelerometer are sent to Plaspy for immediate logging and alerting.
  • Device connectivity and health appear in Plaspy to support maintenance and uptime monitoring.
  • Plaspy uses the same port for all supported devices and automatically detects the tracker protocol, simplifying multi-device deployments.

Common Configuration Workflow​

  1. Access the official manufacturer configuration method or software, for example Syrus Desk or the Pegasus Gateway IoT Platform.
  2. Prepare APN values for the device and enter them in the configuration (use the [apn], [apnu], and [apnp] placeholders if required by the script).
  3. Enter d.plaspy.com or 54.85.159.138 as the remote server address in the device configuration.
  4. Set the port to 8888 and choose UDP or TCP if the device requires selecting a transport.
  5. Apply or save the configuration in the manufacturer tool and upload or push the script/profile to the Titan Tracker.
  6. Restart the device if required by the firmware to apply the new network and server settings.
  7. Validate that the device reports to Plaspy by checking device visibility and received events on the Plaspy platform.

Example Configuration Commands​

The manufacturer provided a Syrus SB script example that can be saved with a .tmf extension and loaded with Syrus Desk. The commands below are presented in the same order as the example script and include placeholders for APN settings.

  • Save the following text as a new file with a .tmf extension and load it in Syrus Desk to apply the configuration.
# Syrus SB script
# Getting Started example
# Delete any previous configuration
>SRT;CONFIG<
>SXADP**U<
# configuring the APN
>SRFA[apn]<
>SRFI<
>SRFL[apnu]<
>SRFP[apnp]<
# The remote AVL server address and port
>SXADP0000d.plaspy.com;8888<
# A Destination Address holding the server destination
>SDA4;P00<
# Time-only Time And Distance signal definition
>STD80300<
# Event triggered by T&D signal
>SED37NV4;TD8+<
# Input report event
>SED05NV4;IP3+<
# end

Notes on the commands above:

  • SRT;CONFIG< is included in the script to delete any previous configuration; treat this as an optional initial reset when starting a fresh configuration.

  • The APN placeholders [apn], [apnu], and [apnp] must be replaced with your mobile operator APN, APN username, and APN password where required.
  • The remote server address is set to d.plaspy.com with port 8888 in the SXADP command. You can replace the domain with the IP 54.85.159.138 if preferred.
  • The example uses device-specific Syrus SB commands; load the .tmf into Syrus Desk and push to the device per manufacturer instructions.

Configuration Notes​

  • Firmware and SKU differences can change the exact command set and behavior; always confirm the available commands for your device firmware version before applying a script.
  • When given the choice, select UDP or TCP based on your network and reliability requirements; Plaspy accepts both and detects the protocol automatically on port 8888.
  • Replace the APN placeholders [apn], [apnu], and [apnp] with operator-specific values; leaving placeholders unchanged will prevent the device from establishing a data connection.
  • Use Syrus Desk or the manufacturer device management tool to import the .tmf script and to review any device response or upload logs.
  • Because Plaspy uses the same port for all supported devices, you do not need a unique port per device when pointing trackers to Plaspy.

Why Use Plaspy with This Configuration​

Using the Titan Tracker with Plaspy provides organizations with unified visibility into location, safety alerts, and event telemetry. The tracker’s SOS button, accelerometer-driven motion and impact detection, and rugged portable design complement Plaspy’s dashboards and alerting to support worker safety, asset tracking, and operational oversight.

Learn more about Plaspy and how it integrates with devices like the DCT Titan Tracker at https://www.plaspy.com. Device-specific configuration methods, firmware behavior, and manufacturer details can change over time; verify the latest setup instructions and technical documentation at the manufacturer site https://www.digitalcomtech.com/ before deployment.

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