Skip to main content

Autoseeker - AT-16 Configuration

This page documents the public configuration context for using the Autoseeker AT-16 OBD GPS tracker with Plaspy. It covers the practical server settings Plaspy requires, the typical workflow to point the AT-16 at the Plaspy platform, and the common prerequisites you should check before integration. The AT-16 is a plug-and-play OBD device that is Plaspy compatible out of the box and can report location and vehicle telemetry to a third party platform.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol, while manufacturer-side setup can vary by firmware, hardware revision, installation type, and vendor tools. This guide centers on the public Plaspy connection values you will use when configuring the AT-16 and explains the basic steps and checks that are generally required. Always verify device-specific commands and SMS formats in the official Autoseeker documentation.

Configuration Overview​

The goal of configuration is to prepare the AT-16 to send location and event data to Plaspy so devices appear and update reliably within the platform. Configuration focuses on pointing the device at Plaspy's shared server endpoint and confirming transport and connectivity so telemetry flows continuously.

  • Point the tracker to the Plaspy server endpoint so data is delivered to the correct destination.
  • Configure transport mode (UDP or TCP) and the shared Plaspy port so the device can establish a session.
  • Verify SIM and network connectivity if using the device's GSM data channel for reporting.
  • Apply and save settings on the tracker and confirm it begins reporting to Plaspy.
  • Validate visibility in Plaspy by checking incoming messages and basic telemetry such as location and ignition state.

Plaspy Server Settings​

Use these public Plaspy connection values when configuring the AT-16:

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support for UDP or TCP on port 8888
  • Plaspy automatically detects the tracker protocol and uses the same port for all supported devices

These values are the shared server settings Plaspy expects for device connections.

Typical Requirements Before Setup​

  • Access to the vehicle OBD port and the ability to plug in the AT-16 device.
  • Powered device with an active 2G GSM SIM card configured for data and SMS if you will use the tracker’s cellular reporting features.
  • Credentials and access to your Plaspy account so you can validate device reporting once configured.
  • Access to the official Autoseeker configuration methods such as SMS commands, PC configuration software, or vendor setup tools.
  • A note of the device IMEI or serial number to match the tracker with the Plaspy fleet record.
  • Basic knowledge of whether your installation requires UDP or TCP selection based on installer preference or local network behavior.

How This Tracker Connects to Plaspy​

When configured to report to Plaspy, the AT-16 sends location points, event notifications, and selected vehicle telemetry to the shared Plaspy endpoint on port 8888. Plaspy receives the data regardless of whether the tracker uses the domain d.plaspy.com or the listed IP, and it will detect the tracker protocol automatically.

  • The device reports GPS position and timestamps to d.plaspy.com or 54.85.159.138 on port 8888.
  • Events such as ignition on/off, unplug alerts, geo-fence triggers, and over-speed can be forwarded to Plaspy for immediate handling.
  • Trip history and telemetry sent by the tracker synchronize with Plaspy for route playback and reporting.
  • Plaspy supports both UDP and TCP transport; configure the AT-16 accordingly and Plaspy will accept the incoming data and detect the protocol automatically.
  • Visibility and operational monitoring in Plaspy depend on successful delivery of packets to the shared Plaspy port 8888.

Common Configuration Workflow​

  1. Access the official Autoseeker configuration method recommended for the AT-16 such as the vendor PC tool, mobile app, or SMS command interface.
  2. Set the server address to d.plaspy.com or enter the server IP 54.85.159.138 in the device configuration field as supported.
  3. Configure the destination port to 8888.
  4. Choose UDP or TCP transport if the device requires a transport selection; typically select the transport preferred for your local network.
  5. Apply or save the configuration on the tracker using the manufacturer tool or SMS save command.
  6. Restart the device if the manufacturer recommends a reboot after configuration.
  7. Validate that the device reports to Plaspy by confirming incoming data appears in your Plaspy account and basic telemetry such as location and ignition status updates.

Example Configuration Commands​

The AT-16 supports configuration via manufacturer tools and SMS commands, but exact commands and syntax can vary by firmware version and vendor toolset. Autoseeker typically documents the available SMS strings and software configuration options in the official manual. Because commands are provided and maintained by the manufacturer, consult the Autoseeker documentation for the precise command set you should use with your device.

If you receive an official SMS command list from Autoseeker, follow the order provided there when sending configuration and save commands. When entering the server address you may use either the domain d.plaspy.com or the IP 54.85.159.138 and set the port to 8888; select UDP or TCP when prompted. Always preserve any required SMS command format and placeholders shown in the manufacturer guide.

Configuration Notes​

  • Firmware and hardware revisions can change available command syntax and configuration workflows; always check the device manual for your specific AT-16 unit.
  • Because the AT-16 uses 2G GSM, confirm that 2G networks are available and supported by your mobile operator in the device deployment region.
  • Choosing UDP versus TCP depends on network reliability and installer preference; Plaspy accepts either transport on port 8888 and detects the protocol automatically.
  • Keep the device IMEI and registration details handy when validating the device in Plaspy to speed up troubleshooting.
  • Use the manufacturer supplied tools or SMS commands for configuration to avoid applying unsupported settings.

Why Use Plaspy with This Configuration​

Using the Autoseeker AT-16 with Plaspy provides a practical, low-effort path to centralized fleet visibility and event-driven workflows. The AT-16’s plug-and-play OBD form factor reduces installation time while delivering telemetry such as ignition state, unplug alerts, and location that Plaspy converts into live tracking, alerts, and historical reports. For fleets, rental operations, and vehicle security deployments, this combination enables timely notifications, route analysis, and audit-ready logs.

To learn more about Plaspy and how it manages device connections and fleet data, visit https://www.plaspy.com. For the latest device-specific commands, SMS formats, firmware notes, and detailed installation instructions for the AT-16, verify details with the manufacturer at https://autoseekergps.com/ as device behavior and setup steps may 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