Sensor Ecosystem

Built-in positioning + motion. Expandable sensor ecosystem.

ninSmart comes with embedded GNSS and IMU for every deployment, then scales with 9× modular Grove/Qwiic ports, OBD-II/CAN/K-Line, dual cameras, and control relays to capture fleet events with regulator-grade evidence.

  • Embedded: GNSS + IMU (standard)
  • Expandable: 9× Grove/Qwiic ports
  • Vehicle data: OBD-II / CAN / K-Line
  • Vision: 2 cameras supported
  • Evidence-ready: timestamp + location + device ID
Section 1

What's built into every ninSmart device

These capabilities are embedded in the main device and do not use any of the 9 Grove/Qwiic ports:

GNSS Positioning

Multi-constellation support depending on configuration

IMU Motion Sensing

Acceleration / turning / vibration signals

Power Health Monitoring

Voltage events, resets, brownouts

Tamper Signals

Enclosure open / detach detection (depending on configuration)

Result: Even with zero add-ons, you have baseline tracking + motion events + device integrity.

Section 2

9× modular ports for add-on sensors

Use the 9 modular ports to connect external sensors and actuators. Typical interfaces include I²C, UART, ADC, GPIO.

Cargo, Door & Asset Monitoring

Examples: door sensor, cargo latch sensor, tilt sensor, vibration tag

Use cases:

Unauthorized opening, cargo safety, delivery integrity

Load & Weight

Examples: load cell / weight sensor, seat/occupancy sensor, pressure mat

Use cases:

Overload detection, payload monitoring, compliance

Proximity & Distance

Examples: LiDAR / ranging sensor, ultrasonic proximity

Use cases:

Obstacle proximity, depot/site safety, maneuver risk indicators

Environmental & Cold Chain

Examples: temperature, humidity, air quality, gas sensors

Use cases:

Cold-chain compliance, cabin safety, environmental reporting

Parking / Stand / Movement State

Examples: kickstand sensor (2-wheel fleets), contact sensors

Use cases:

Misuse detection, parking compliance, operational safety

Custom Sensors

If your sensor outputs I²C/UART/analog/GPIO

Use cases:

We can map it into the ninSmart data model and policies

Section 3

OBD-II / CAN Bus / K-Line (vehicle dependent)

ninSmart can read vehicle/ECU data when available:

Speed / RPM / Ignition status
Odometer (vehicle dependent)
Diagnostic trouble codes (DTC)
Battery/alternator signals

Note: For motorcycles/scooters, ECU access varies by brand/model — ninSmart falls back to embedded GNSS+IMU + cameras when ECU data is limited.

Section 4

Dual-camera support for evidence and AI workflows

Connect up to 2 cameras (typical setup: road-facing + driver-facing / cargo / cabin).

Event-linked Clips

Incident, risky behavior, disputes

Policy-driven Capture

By zone, by threshold, by trigger

Metadata Packaged

Location, time, device ID

Section 5

Actuators & enforcement actions (where permitted)

Optional control modules can be used for:

Engine Cutoff Relay

Policy-driven; jurisdiction/approval dependent

Siren/Light Control

Fleet use cases

Door Lock / Auxiliary

Integrated workflows

Section 6

From sensor signal → compliant event record

4 steps to evidence-grade compliance

1

Capture

Embedded + add-on sensors + vehicle data + cameras

2

Validate

Units, calibration status, sensor health, tamper state

3

Trigger

Policy thresholds, geofences, risk patterns

4

Package

Timestamp, location, device ID, policy version, media, logs

Recommended Kits

Pick a kit by fleet type

GNSS+IMU included by default in every device

Motorcycles & Scooters

Built-in: GNSS + IMU
Add-ons: 2 cameras
Optional: door/cargo sensor
Optional: relay, proximity sensor

Vans & Light Trucks

Built-in: GNSS + IMU
Add-ons: OBD-II/CAN
2 cameras
Door sensor, temp/humidity

Buses / Public Transport

Built-in: GNSS + IMU
Cabin camera option
Multi-zone compliance
Passenger safety sensors

Construction Machinery

Built-in: GNSS + IMU
Proximity/LiDAR
Vibration tag
Site geofencing sensors

Frequently Asked Questions