Skip to main content

Neomatica - ADM007 BLE Configuration

This page provides the public configuration context for using the Neomatica ADM007 BLE tracker with Plaspy. It focuses on the practical server settings and workflow needed to connect the cigarette lighter plug-and-play ADM007 BLE to the Plaspy platform, while using the device's supported Bluetooth, SMS, or GPRS configuration paths where applicable.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol. Exact manufacturer-side steps can vary with firmware version, hardware revision, installation type, and vendor tools; this guide centers on the Plaspy-side values and a practical setup workflow for the ADM007 BLE based on the publicly available device description.

Configuration Overview​

The goal of configuration is to prepare the ADM007 BLE to communicate reliably with Plaspy so the device appears in your fleet, reports position and BLE sensor telemetry, and synchronizes local logs when connectivity returns.

  • Configure the device to send data to the Plaspy server endpoint and port so live GPS and BLE sensor data reach the platform.
  • Verify transport selection (UDP or TCP) and set the shared Plaspy port so the device and server match.
  • Confirm mobile data connectivity and SIM readiness so GPRS uplink is available for reporting.
  • Validate the device appears in Plaspy and that historical logs and sensor telemetry synchronize correctly.
  • Use Bluetooth or the manufacturer's configuration tool for local changes and FOTA when firmware updates are required.

Plaspy Server Settings​

  • Server domain: d.plaspy.com
  • Server IP: 54.85.159.138
  • Port: 8888
  • Transport: device may be configured to use UDP or TCP on port 8888
  • Protocol detection: Plaspy automatically detects the tracker protocol and uses the same port for all supported devices

These values are the public Plaspy endpoint settings to enter in the ADM007 BLE configuration tool or SMS/remote setup interface.

Typical Requirements Before Setup​

  • A vehicle power source or cigarette lighter socket for the ADM007 BLE installation and operation.
  • A NanoSIM with active mobile data to provide GPRS uplink for position and telemetry reporting.
  • Access to the official Neomatica configuration method such as the ADM Configurator mobile app, vendor software, or supported SMS commands when applicable.
  • Bluetooth access for local configuration and FOTA updates if you prefer local management.
  • A Plaspy account and basic access to the platform to confirm device registration and data visibility.
  • Confirmation of current firmware version and device revision from Neomatica before applying settings.

How This Tracker Connects to Plaspy​

When configured for Plaspy, the ADM007 BLE transmits GNSS fixes and BLE sensor readings over its cellular GPRS connection to the shared Plaspy endpoint and port. Plaspy receives and parses the incoming protocol automatically, then surfaces real-time location, telemetry, and alerts in the platform.

  • The tracker is set to report to the Plaspy server endpoint d.plaspy.com on port 8888.
  • Data transport can be either UDP or TCP depending on device settings; configure the tracker accordingly.
  • BLE sensor telemetry is sent alongside GNSS fixes so Plaspy can display sensor readings with location context.
  • Local route logging is synchronized to Plaspy when GPRS connectivity is available for full trip history.
  • Anti-jamming or tampering alerts generated by the device are forwarded to Plaspy for monitoring and notification.

Common Configuration Workflow​

  1. Access the official Neomatica configuration method such as the ADM Configurator app over Bluetooth or the manufacturer tool provided by your vendor.
  2. In the device server settings, enter the Plaspy server host as either d.plaspy.com or the IP 54.85.159.138.
  3. Set the server port to 8888 (this is the same port Plaspy uses for all supported devices).
  4. Choose the transport protocol (UDP or TCP) if the device requires a transport selection.
  5. Apply or save the configuration changes in the manufacturer tool or via the supported configuration channel.
  6. Restart or power cycle the ADM007 BLE if the manufacturer instructions indicate a restart is required to apply network changes.
  7. Validate on Plaspy that the device is reporting and that location and BLE sensor telemetry are visible in the platform.

Example Configuration Commands​

The ADM007 BLE can be configured using Neomatica tools, Bluetooth ADM Configurator, SMS commands, or vendor software depending on the firmware and distribution channel. Exact command syntax and availability vary by firmware and tool; consult Neomatica documentation or your vendor for the exact commands and message formats required to set the server host, port, and transport.

If you are using a manufacturer-provided SMS interface or configuration strings, enter the Plaspy host as d.plaspy.com or 54.85.159.138 and set the port to 8888, selecting UDP or TCP according to the device option. Because command formats differ across firmware, this page does not list device-specific SMS strings; reference the official Neomatica command guide for exact commands.

Configuration Notes​

  • Firmware differences: command formats, available transport options, and menu names can vary between firmware versions and hardware revisions.
  • TCP versus UDP: choose UDP for lower overhead and reduced latency in many tracking setups, or TCP if your environment requires connection-oriented delivery; Plaspy supports both on port 8888.
  • BLE sensor behavior: BLE telemetry is reported as part of the device uplink when the ADM007 BLE aggregates sensor data; verify sensor pairing and reporting intervals in the device settings.
  • Local logging: the ADM007 BLE stores local route records while offline and synchronizes with Plaspy when connectivity returns.
  • Manufacturer documentation: rely on Neomatica documentation for exact SMS strings, app workflows, and FOTA procedures.

Why Use Plaspy with This Configuration​

Using the ADM007 BLE with Plaspy simplifies deployment for operators who need quick installation and reliable telematics. The plug-and-play cigarette lighter form factor, combined with BLE sensor support and efficient mobile data usage, makes it practical to deploy across temporary fleets, rentals, or anti-theft use cases while keeping monitoring and historical reporting centralized in Plaspy.

To learn more about Plaspy and how the platform manages device connectivity and fleet data, visit https://www.plaspy.com. For the most current device-specific setup details, firmware behavior, and official command references, verify the latest information on the Neomatica website https://neomatica.com/.

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