Skip to main content

Reachfar - RF-V6+ Configuration

This page covers the public configuration context for using the Reachfar RF-V6+ tracker with the Plaspy fleet and asset tracking platform. It explains the shared server settings Plaspy requires and outlines practical setup steps and validation guidance you can follow when integrating the RF-V6+ for real time tracking and alarm reporting.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol, while exact manufacturer side setup steps can vary by firmware, hardware revision, installation type, and vendor tools. Use the guidance below to prepare the RF-V6+ for Plaspy and consult Reachfar documentation for device specific commands and the most current firmware behavior.

Configuration Overview​

This configuration process prepares the RF-V6+ to send position, alarm and status data to Plaspy so the device becomes visible and actionable inside the platform. The steps below focus on configuring the device to point at the Plaspy endpoint, validating connectivity, and ensuring data appears in Plaspy.

  • Configure the RF-V6+ to report over GPRS TCP/IP to the shared Plaspy endpoint and port.
  • Select transport (UDP or TCP) if the device requires an explicit choice.
  • Validate network connectivity and APN settings so GPRS reporting succeeds.
  • Save and apply configuration, then verify the device reports to Plaspy and alarms are visible.
  • Use SMS or app controls as fallback methods for verification or when GPRS is unavailable.

Plaspy Server Settings​

Use the following public Plaspy server settings when configuring the RF-V6+ to report to Plaspy. Plaspy uses the same port for all supported devices and automatically detects the tracker protocol.

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support for UDP or TCP depending on device selection
  • Automatic protocol detection in Plaspy so no per device protocol registration is required on the platform side

Typical Requirements Before Setup​

  • A charged RF-V6+ with access to its configuration method via the manufacturer app, SMS commands, or vendor tool.
  • A valid SIM card provisioned for 2G GPRS data and SMS if you plan to use GPRS TCP/IP reporting and SMS controls.
  • Knowledge of the carrier APN and any authentication credentials required by the SIM; have APN details ready for configuration.
  • Access to Reachfar configuration instructions or software from the device vendor or distributor for the exact command set.
  • A basic test plan to confirm device power, network registration, GPRS session establishment, and reporting to the Plaspy endpoint.

How This Tracker Connects to Plaspy​

When configured for GPRS TCP/IP reporting the RF-V6+ opens a data session and sends periodic position and event packets to the Plaspy server endpoint and port. Plaspy receives the stream, automatically detects the tracker protocol, and presents the device data in the platform for monitoring and alerts.

  • The device sends location updates and telemetry to the shared Plaspy server endpoint d.plaspy.com or 54.85.159.138 on port 8888.
  • Plaspy accepts either UDP or TCP transport depending on device configuration and automatically detects the device protocol.
  • Alarms such as SOS, vibration tamper, and geo fence events are reported as discrete messages to Plaspy for alerting.
  • SMS based queries and alarm messages can be used as a fallback when GPRS reporting is unavailable or for remote verification.

Common Configuration Workflow​

  1. Access the official Reachfar configuration method or software provided by the manufacturer or your vendor.
  2. In the TCP IP or server settings, enter the Plaspy server address using either d.plaspy.com or the server IP 54.85.159.138.
  3. Set the server port to 8888. Note that Plaspy uses the same port for all devices.
  4. If the device requires a transport selection, choose UDP or TCP according to your deployment preference.
  5. Configure APN and any SIM credentials required for GPRS connectivity, then apply or save the settings.
  6. Restart the device if the vendor instructions require a reboot for changes to take effect.
  7. Validate the device reports to Plaspy by checking for incoming position updates and test alarm events in the platform.

Example Configuration Commands​

The exact command syntax and methods for the RF-V6+ depend on the Reachfar firmware and the configuration interface you use. Because model specific commands are provided by Reachfar or resellers, the precise SMS or software commands are not included here. Typical configuration methods include:

  • Using the Reachfar mobile app or web tool to set the server, port, APN, and transport.
  • Sending manufacturer SMS commands to set the server address, server IP, port, and APN when SMS configuration is supported.

Refer to the official Reachfar configuration guide or the device vendor for the exact commands and examples needed for your firmware version.

Configuration Notes​

  • Firmware and hardware revisions may change the exact SMS commands or menu layouts used to set the server and APN. Always confirm commands with the manufacturer documentation.
  • Choose TCP or UDP based on network stability and your preferences; Plaspy supports both transports and will detect the tracker protocol automatically.
  • If you use SMS for configuration or fallback reporting, verify SMS formats and firewall rules with your SIM provider to ensure message delivery.
  • Some older RF-V6+ firmware variants may require different command formats or ordering when applying server parameters; test on a single device before bulk deployment.
  • Keep a record of APN and SIM related credentials to simplify mass configuration and troubleshooting.

Why Use Plaspy with This Configuration​

Using the Reachfar RF-V6+ configured to report to Plaspy gives a compact, reliable option for discreet asset and vehicle tracking with real time location and alarm reporting. Plaspy aggregates position updates, alarm events, and historical routes so operators can monitor assets, review incident history, and build location based workflows from a central platform.

To learn more about Plaspy visit https://www.plaspy.com and for the latest device specific setup details and firmware notes check the Reachfar official site https://www.reachfargps.com/. Manufacturer specifications, setup methods, and device behavior can change over time so verify current configuration commands and firmware behavior with Reachfar documentation before large scale 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