Skip to main content

Falcom - FOX3-2G Configuration

This page describes the public configuration context for using the Falcom FOX3-2G tracker with the Plaspy platform. It focuses on the practical server settings and the general steps you will perform on the device or in Falcom configuration tools to enable the FOX3-2G to report to Plaspy for location visibility and event reporting.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol so most configuration tasks involve pointing the device at the Plaspy endpoint and choosing the transport type. Manufacturer-side steps for Falcom devices can vary by firmware, hardware revision, installation type, and vendor tools, so consider the Falcom documentation and your installer tools when applying the settings below.

Configuration Overview​

This configuration process prepares the FOX3-2G to communicate reliably with Plaspy, validates connectivity, and enables device visibility and reporting in the Plaspy platform.

  • Point the device to the Plaspy server endpoint so telemetry and events are routed to your Plaspy tenant.
  • Choose the transport protocol supported by the device and Plaspy, typically UDP or TCP.
  • Save and apply the settings in the Falcom configuration tool or device interface.
  • Confirm the device registers and sends position and status messages to Plaspy.
  • Validate alerts, geofence events, and status reports in Plaspy once the device is online.

Plaspy Server Settings​

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support for UDP or TCP
  • Automatic protocol detection in Plaspy

Typical Requirements Before Setup​

  • Ensure the FOX3-2G is powered and properly wired according to installer guidelines.
  • Active 2G SIM with a suitable data plan and correct APN configured for the device.
  • Access to the official Falcom configuration method or software used by your installer.
  • Knowledge of the device firmware version and any vendor tools that apply settings.
  • A Plaspy account or provisioning process ready so the device can be registered and validated in the platform.

How This Tracker Connects to Plaspy​

The FOX3-2G sends its GNSS positions and device status to the shared Plaspy server endpoint and port so Plaspy can display real time locations and recorded events. Plaspy automatically detects the tracker protocol so devices using different protocols can be handled without per device protocol mapping.

  • Periodic position reports are sent to d.plaspy.com or 54.85.159.138 on port 8888 using UDP or TCP.
  • Status reports and configured alerts are forwarded to the Plaspy platform for monitoring.
  • Geofence and event messages generated by the tracker appear in Plaspy once the device is reporting.
  • Plaspy receives the traffic on the same port used for all supported devices and applies automatic protocol detection.

Common Configuration Workflow​

  1. Access the official Falcom configuration method or software provided by the vendor or installer.
  2. In the device server settings enter d.plaspy.com or 54.85.159.138 as the target server.
  3. Set the server port to 8888 as required by Plaspy.
  4. Choose UDP or TCP if the FOX3-2G requires a transport selection in the configuration interface.
  5. Apply or save the configuration in the Falcom tool and confirm there are no configuration errors.
  6. Restart the device if the device or firmware requires a reboot for network settings to take effect.
  7. Validate that the FOX3-2G reports to Plaspy and appears in your Plaspy account or monitoring view.

Example Configuration Commands​

The exact configuration method for the FOX3-2G depends on the Falcom configuration utility, firmware version, and installer procedure. Plaspy expects the device to be pointed to d.plaspy.com or 54.85.159.138 on port 8888 and will accept connections over UDP or TCP. Use the Falcom configuration software or the manufacturer provided instructions to set these values. If your installation uses text or SMS commands provided by Falcom, follow the official command set from Falcom for setting the server and port.

Configuration Notes​

  • Falcom firmware revisions and configuration tools can change how server and transport settings are entered; always check the Falcom release notes for your device version.
  • Plaspy uses the same port 8888 for all supported devices and will automatically detect the tracker protocol, so the same port and endpoint are typically used across deployments.
  • Choosing UDP or TCP can affect message delivery and retry behavior; select the transport supported by your device and aligned with your operational needs.
  • The FOX3-2G supports internal and external antennas; verify antenna selection and placement during installation for best GNSS and cellular reception.
  • If you extend functionality with IOBOX-MINI or IOBOX-CAN, confirm those modules do not alter the network reporting settings required for Plaspy.

Why Use Plaspy with This Configuration​

Using the FOX3-2G with Plaspy provides a straightforward path to capture location, status, and event data from Falcom devices and present it in a central fleet management platform. The shared Plaspy server settings and automatic protocol detection reduce per device complexity so installers can focus on reliable hardware installation and correct APN configuration.

To learn more about Plaspy and how it can integrate with Falcom trackers visit https://www.plaspy.com. For the latest device specific instructions firmware notes and configuration commands consult the official Falcom documentation at https://www.falcom.de to verify current setup methods and manufacturer details.

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