Skip to main content

Riti - 670 (IDU-300) Features

This page summarizes the public feature context for using the Riti Locator 670 (IDU-300) with Plaspy. It focuses on the practical capabilities this in vehicle GPS tracker brings to Plaspy deployments, how those capabilities become visible inside Plaspy, and what operational value fleet teams can expect from integrating this device with the platform.

Exact feature availability and behavior can vary by firmware version, hardware revision, installation method, and the manufacturer implementation. The Locator 670 is a discontinued 3G IDU model, so deployment characteristics for legacy fleets or mixed environments should be verified against current device firmware and Riti documentation.

Feature Overview​

The Locator 670 is a Plaspy compatible in vehicle GPS tracker designed for frequent position reporting and multi sensor telemetry. It is positioned for fleet managers who need reliable location visibility, per second mileage reporting, battery voltage monitoring, and extended peripheral support for workflows such as cold chain and asset protection.

  • Real time position reporting with frequent updates for responsive fleet visibility
  • High sensitivity GNSS receiver for improved satellite lock in challenging environments
  • Per second mileage and odometer reporting for accurate trip and utilization analytics
  • Battery voltage monitoring to detect low voltage conditions and alert operators
  • Support for temperature sensors, fuel level inputs, DVR and peripheral integration for extended telemetry
  • Local data buffering to preserve records during temporary connectivity loss and upload when cellular recovers

Core Features of Riti - 670 (IDU-300)​

  • Plaspy compatible real time GNSS tracking for live mapping and monitoring
  • High sensitivity GNSS receiver providing stronger satellite lock and reliable fixes
  • Frequent position reporting capable of updates as often as every 15 seconds
  • Per second mileage calculation for more accurate odometer and route analytics
  • Battery voltage monitoring to surface low voltage conditions in Plaspy
  • Broad peripheral and I O support including temperature sensor inputs and fuel level inputs
  • Local data buffering with automatic uplink when connectivity is restored
  • Remote diagnostics and firmware update support to aid maintenance and keep units aligned with Plaspy

How These Features Work with Plaspy​

When a Locator 670 is integrated with Plaspy, its GNSS positions and connected sensor telemetry are forwarded to the platform so teams can monitor vehicles on live maps, review historical trips, and act on exception conditions. Plaspy ingests the device feed and exposes location and telemetry in reports, alerts, and event logs.

  • Live location updates and map visibility based on frequent position reports
  • Trip and utilization reports that use per second mileage for cleaner route analytics
  • Battery voltage readings surfaced as telemetry fields and used to trigger low voltage alerts
  • Temperature and fuel level inputs forwarded into Plaspy for cold chain and fuel monitoring workflows
  • Peripheral events such as DVR alerts, SOS triggers, and external input events recorded in event logs
  • Local buffering ensures records generated offline are uploaded and reconciled by Plaspy when connectivity returns

Typical Use Cases​

  • Fleet management and dispatch for trucks, delivery vehicles, and service fleets requiring responsive location tracking
  • Cold chain and temperature controlled deliveries using temperature sensor inputs and Plaspy alerts
  • Vehicle safety and emergency fleet monitoring where SOS events and synchronized DVR events are important
  • Fuel and asset monitoring through fuel level inputs and external reader integrations
  • MDVR and telematics integrations where RS 232 and multiple I O allow synchronized event data
  • Legacy fleet support where the discontinued 3G IDU model remains in service within a mixed deployment

Feature Availability Notes​

  • The Locator 670 is a discontinued 3G IDU model; feature availability for new deployments should be evaluated against current cellular network and vendor recommendations
  • Specific features and peripheral compatibility can vary by firmware version and hardware revision from the manufacturer
  • Installation type and wiring determine which inputs and outputs are usable in a particular vehicle
  • Regional variants and network support may affect functionality in some markets
  • Always consult the official Riti documentation for the definitive list of supported peripherals and hardware specifications

Why Use Plaspy with These Features​

Using the Riti Locator 670 with Plaspy gives operations teams consolidated visibility into vehicle location, mileage, battery health, and peripheral telemetry. Plaspy converts the device data feed into live maps, alerts, and historical reports that support dispatch decisions, preventive maintenance, and compliance workflows.

To learn more about how Plaspy can work with Riti devices and other compatible trackers, visit https://www.plaspy.com. For the most current device specific details, firmware notes, and manufacturer implementation information verify features on the official Riti site https://www.riti.com.tw/.

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