Skip to main content

Falcom - STEPPIII-UX Features

This page covers the public feature context for using the Falcom STEPPIII-UX tracker together with Plaspy. It summarizes the model's main capabilities and explains how those capabilities are commonly used within Plaspy for AVL, fleet management, vehicle security, and recovery scenarios. The information here is written for a general technical audience and focuses on practical, non-sensitive details relevant to integration and operation.

Exact feature availability can vary depending on device firmware, hardware revision, installation type, and how the manufacturer configures the unit for a given deployment. Where useful, this page highlights behaviors described in Falcom documentation, but users should confirm current, device-specific details with the manufacturer and the installer prior to mission-critical use.

Feature Overview​

The STEPPIII-UX is a flexible, configurable tracking client designed to serve a range of vehicle and asset monitoring use cases. It combines autonomous operation, configurable communications, and logging features intended to integrate into existing tracking systems.

  • Tailorable operation for AVL, fleet management, vehicle security, and recovery use cases.
  • Configurable communications to send status reports and alerts to servers via TCP and to users via SMS.
  • Autonomous operation with the ability to interact with connected sensors and actors for customized behavior.
  • Support for voice calls including regular calls and emergency spy calls when enabled.
  • Driver logbook and onboard data logging with integration into Falcom history features for event and trip records.
  • Geofencing support to define zones or routes and generate notifications on entry or exit.

Core Features of Falcom - STEPPIII-UX​

  • Mobile client capabilities for AVL and fleet management deployments.
  • Configurable reporting and alerting over TCP to tracking servers and SMS to users.
  • Autonomous device behavior with interfaces to external sensors and actors for customized workflows.
  • Regular voice call capability plus emergency spy call functionality.
  • Driver logbook and data logging that integrate with Falcom history and reporting.
  • Geofencing to detect and report area or route boundary crossings.
  • High configurability to tailor reporting intervals, event rules, and message content to operational needs.

How These Features Work with Plaspy​

Plaspy serves as the receiving platform for device reports and events from compatible trackers such as the STEPPIII-UX. When configured to report to Plaspy, the tracker’s events and status messages become visible within the Plaspy interface for monitoring and operational use.

  • Location reports and movement updates from the device appear as position updates in Plaspy maps and timelines.
  • Alerts and status messages sent to the tracking server are reflected as events that can be reviewed and filtered in Plaspy.
  • Driver logbook entries and device data logging are represented as history records, aiding trip review and compliance checks.
  • Geofence entry and exit notifications generated by the device are delivered into Plaspy as geofence events for monitoring and reporting.
  • Plaspy detects supported tracker protocols automatically and ingests the information the device sends, allowing devices to be used with minimal protocol setup.

Typical Use Cases​

  • Centralized fleet tracking and route compliance monitoring for commercial vehicle fleets.
  • Vehicle security and recovery workflows where location and alert reporting assist response teams.
  • Operational oversight with driver logbook review and historical trip analysis.
  • Remote monitoring of mobile assets that require event-based reporting and custom alerting.
  • Geofence-based site control for worksites, depots, or restricted areas.

Feature Availability Notes​

  • Feature presence and behavior may vary with device firmware level and hardware revision.
  • Some capabilities depend on how the device is configured by the installer or vendor for a specific deployment.
  • Voice call and SMS behaviors depend on telephony configuration and mobile network availability.
  • Geofencing, logging granularity, and event rules can be enabled or tuned during setup and may be optional in some variants.
  • Always consult Falcom documentation and the device’s configuration guide for the exact list of supported functions for a given unit.

Why Use Plaspy with These Features​

Using the Falcom STEPPIII-UX with Plaspy gives organizations a practical path to capture its configurable tracking and alerting capabilities inside a centralized monitoring platform. Plaspy translates device reports and events into position history, event timelines, and geofence alerts, helping operations teams keep visibility into vehicle activity and respond to exceptions.

If you want to explore how the STEPPIII-UX can be deployed with Plaspy in your environment, learn more about Plaspy at https://www.plaspy.com. For the most current, device specific details and firmware guidance, please verify information with the manufacturer at https://www.falcom.de as features and implementations can change over time.

Tracker Capabilities

See how these features fit into Plaspy

Plaspy helps turn compatible tracker capabilities into useful visibility, monitoring, and operational workflows across vehicles and assets.

Learn more about Plaspy