Skip to main content

iTriangle - OBD II Features

This page provides the public feature context for using the iTriangle OBD II tracker with Plaspy. It summarizes the model's practical capabilities, describes how its telemetry and telemetry sources are used in Plaspy, and explains the typical operational value this plug and play device brings to fleet and vehicle monitoring workflows.

Exact feature availability and behaviour can vary by firmware version, hardware revision, vehicle make and model, installation type and manufacturer implementation. For device specific technical details and the latest firmware notes consult the official iTriangle documentation and release notes.

Feature Overview

The iTriangle OBD II is a compact OBD II plug and play tracker designed for fast installation and continuous vehicle telemetry. It combines GNSS positioning, cellular connectivity, Bluetooth radio and OBD/CAN access in a single unit intended for commercial fleet and rental vehicle deployments.

  • Plug and play OBD II installation for rapid deployment without splicing or permanent wiring.
  • GNSS positioning using GPS and GLONASS for reliable location fixes and historical trails.
  • Built in cellular and Bluetooth antennas to reduce installation complexity and maintain clean vehicle fittings.
  • OBD II and CAN bus access to read common vehicle telemetry and diagnostic PIDs where the vehicle supports them.
  • OTA FOTA remote firmware update capability and remote configuration options to reduce field service.
  • Low sleep current and an internal backup battery to preserve basic reporting during power interruptions.

Core Features of iTriangle - OBD II

  • OBD II plug form factor for quick installation and removal from the vehicle diagnostic port.
  • GNSS support with combined GPS and GLONASS positioning for improved fix availability.
  • Internal cellular radio supporting quad band 2G connectivity for wide coverage in target regions.
  • CAN bus access and OBD II PID reading where supported by the vehicle for engine and diagnostic data.
  • Built in Bluetooth radio to pair short range accessories and transport additional sensor data.
  • Built in accelerometer and tamper alert for basic motion and security event detection.
  • Remote management support including OTA FOTA firmware updates and configuration via supported channels.

How These Features Work with Plaspy

When the iTriangle OBD II is connected to Plaspy, the device's position fixes, OBD II telemetry and sensor events are reported to the platform so operators can view live location, historical trips, diagnostic indicators and security events in one place. Plaspy automatically interprets common tracker signals and surfaces them for reporting and alerting.

  • Real time location and historical trails are available in Plaspy using GNSS fixes from the device.
  • OBD II and CAN records such as supported PIDs and diagnostic codes are ingested into Plaspy dashboards where vehicle support is present.
  • Motion, tamper and power loss events generated by the device are reported to Plaspy for security and incident workflows.
  • Remote firmware updates and configuration changes can be coordinated alongside Plaspy fleet management to minimize onsite maintenance.
  • BLE paired sensor data and accessory identifiers can be relayed through the device into Plaspy for supplementary asset context.

Typical Use Cases

  • Fleet management and dispatch: rapid installation and centralized tracking for mixed vehicle fleets.
  • Preventive maintenance and remote diagnostics: monitor supported OBD II PIDs and diagnostic codes to plan service.
  • Rental and shared vehicle programs: quick deployment and retrieval without hard wiring, with telemetry for usage tracking.
  • Anti theft and security monitoring: tamper alerts and location reporting to assist recovery workflows.
  • Asset augmentation with BLE sensors: relay short range sensor data into fleet records for richer reporting.

Feature Availability Notes

  • OBD II PID support and the exact diagnostic data available depend on the vehicle make, model and year and may vary by region.
  • Bluetooth sensor compatibility depends on the sensor type and pairing method supported by the device firmware.
  • Firmware revisions and hardware variants can add, change or remove features over time; OTA update support reduces the need for physical service but does not guarantee specific capabilities on all units.
  • Power source, installation quality and vehicle electrical systems can affect backup reporting during power loss.
  • Consult iTriangle documentation for regional cellular band support and any regulatory limitations in your deployment area.

Why Use Plaspy with These Features

Using the iTriangle OBD II with Plaspy gives organizations a straightforward path from device deployment to operational visibility. The plug and play form factor reduces installation time, and the combination of GNSS positioning with OBD II telemetry lets operators correlate location with vehicle health and usage. Plaspy brings those signals together into live maps, historical reports, alerts and workflow integrations to support fleet efficiency, preventive maintenance and incident response.

Learn more about Plaspy and how it can integrate device telemetry into your fleet workflows at https://www.plaspy.com. For the most current device specifications, firmware behavior and manufacturer guidance please verify details with the official iTriangle documentation at https://www.itriangle.net/.

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.