Skip to main content

Jointech - JT 600 Configuration

This page documents the public configuration context for using the Jointech JT 600 tracker with the Plaspy platform. It summarizes the server settings Plaspy requires and the practical setup steps that are commonly used to point a JT 600 device at Plaspy for reporting. The content below uses the JT 600 description as the grounding for practical setup advice and includes manufacturer-style SMS commands where publicly available.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol. Exact manufacturer-side steps can vary by firmware version, hardware revision, installation type, and vendor configuration tools. The JT 600 supports GPRS-based reporting and can be configured by SMS commands as shown in the manufacturer guidance included below.

Configuration Overview​

The goal of the configuration steps is to prepare a JT 600 so it reliably communicates location and event data to Plaspy and appears in your Plaspy account. Configuration typically involves setting the device GPRS server target, confirming APN and credentials when required, and validating that the tracker is visible in the platform.

  • Point the JT 600 to the Plaspy server endpoint and confirm transport settings.
  • Provide the correct APN and optional APN credentials so the device can use mobile data or re-upload via GPRS.
  • Save and apply settings on the device, using SMS or the manufacturer tool, then restart if required.
  • Validate connectivity and that the device reports location, SOS, and historical data to Plaspy.
  • Use the shared Plaspy server settings so multiple device models can be managed consistently.

Plaspy Server Settings​

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport can be configured as UDP or TCP depending on device requirements
  • Plaspy automatically detects the tracker protocol when the device connects

Plaspy uses the same port for all supported devices and performs automatic protocol detection to simplify device-side setup.

Typical Requirements Before Setup​

  • A powered and accessible JT 600 device with a valid device ID available
  • A SIM card with data enabled and the correct APN settings for the mobile operator
  • Access to the manufacturer configuration method such as SMS commands or the official Jointech configuration tool
  • The APN name and optional APN username and password for the SIM operator
  • An SMS-capable phone or SMS gateway if configuring the device by SMS
  • A Plaspy account and the ability to verify the device has connected to the platform

How This Tracker Connects to Plaspy​

The JT 600 is configured to send location and event data to the Plaspy shared server endpoint and port. Once the server and APN are set, the device will use GPRS to connect and transmit its reports where Plaspy handles protocol detection and processing.

  • The device is pointed at d.plaspy.com or the IP 54.85.159.138 on port 8888
  • You can choose UDP or TCP transport when the tracker requires a selection
  • Plaspy detects the tracker protocol automatically and processes incoming data
  • Location reports, SOS alerts, geo fence events, and historical uploads are forwarded to Plaspy for display and reporting
  • Successful configuration makes the JT 600 visible in Plaspy for monitoring and alerts

Common Configuration Workflow​

  1. Access the official Jointech configuration method such as the manufacturer SMS commands or Jointech configuration software.
  2. Enter the Plaspy server address using either d.plaspy.com or the IP 54.85.159.138 as the target.
  3. Set the port to 8888 in the device configuration.
  4. Choose UDP or TCP transport if the JT 600 requires a transport selection.
  5. Provide the mobile operator APN and optional APN user and password so GPRS connections can be established.
  6. Apply or save the configuration and restart the device if the device or firmware requires a reboot for changes to take effect.
  7. Validate that the device is reporting and visible in Plaspy and that location and event messages are arriving.

If you are using SMS-based setup, include the device ID in commands and follow the manufacturer order for setting server and APN values.

Example Configuration Commands​

The JT 600 can be configured by sending SMS commands to the device. Replace [trackerID] with the device IMEI or configured device ID and replace the APN placeholders with the correct values for your mobile operator.

  1. Set the GPRS server and APN Send this SMS to the tracker, replacing placeholders as needed:
([trackerID],2,S02,129,1,54.85.159.138,8888,[apn])

You may alternatively use the server domain in the same command if the device accepts a hostname:

([trackerID],2,S02,129,1,d.plaspy.com,8888,[apn])
  1. (Optional) Set the APN user and password If your APN requires credentials, send this SMS:
([trackerID],2,S24,129,1,[apnu],[apnp])

Notes on placeholders

  • [trackerID] — Replace with the device ID or IMEI as required by the tracker.
  • [apn] — Replace with your mobile operator APN name.
  • [apnu] — Replace with the APN username if required by your operator.
  • [apnp] — Replace with the APN password if required by your operator.

Follow the manufacturer order when sending commands; the server/APN command typically should be applied before optional credential commands.

Configuration Notes​

  • Firmware differences or regional firmware builds can change available SMS syntax or parameter order; always confirm with the device documentation.
  • Use UDP or TCP based on installer preference or network conditions; Plaspy supports both and will detect protocol automatically on connection.
  • SMS-based configuration is commonly supported by the JT 600 but installer tools and PC utilities may also be available from Jointech.
  • If your APN does not require a username or password, the second SMS command for credentials can be skipped.
  • Because Plaspy uses the same port across devices, the only device-specific server settings you typically need to set are server address, APN, and transport.

Why Use Plaspy with This Configuration​

Using the JT 600 with Plaspy gives organizations a straightforward path to centralize location, alerts, and operational status across a fleet or dispersed assets. Pointing the JT 600 to the shared Plaspy server endpoint simplifies deployment because the platform handles protocol detection and data parsing once the device connects.

To learn more about how Plaspy handles device connectivity and platform features visit https://www.plaspy.com. For the latest device-specific commands, firmware notes, and manufacturer documentation verify configuration details at the Jointech website https://www.jointcontrols.com/ as setup methods and firmware behavior can change over time.

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