Nine devices, one platform, one login. The right one depends on three things: whether the asset has power, whether you need engine data, and how long it has to run untouched. Start with the question below, then check the full matrix.
Almost every fleet splits into powered vehicles and unpowered assets. They need different hardware, and the difference is not a preference — it is whether there is a port to plug into.
Cars, vans, light trucks. Plugs into the diagnostic port in about a minute and pulls engine telemetry, fault codes, odometer, and driver behaviour alongside location. Powered by the vehicle, so battery life is not a consideration.
Trailers, containers, chassis, gensets, rental equipment, and vehicles you would rather not wire. Self-powered by battery or solar, mounted once and left for years. Location, motion, and tamper — no engine data.
For manufacturers and integrators engineering telematics into the machine. Dual CAN, J1939, a Linux runtime, Wayne AI signal mapping, and an optional Starlink variant for sites cellular does not reach.
All nine devices report into the same iMatrix Cloud, on one login, one alert model, and one API. Every plan includes the EdgeUplink eSIM. You own the hardware outright on every SKU.
| FC-201 OBD-II |
FC-202 Wired |
FC-501 Gateway |
FC-101 Battery |
FC-103 Rugged |
FC-101S Solar |
FC-101S-EX Solar + I/O |
FC-101S-PRO Solar Pro |
FC102C Smart Label |
|
|---|---|---|---|---|---|---|---|---|---|
| Fit | What it is for | ||||||||
| Best for | Cars, vans, light trucks | Heavy equipment with no OBD-II port | OEM programs, heavy equipment | High-value assets, dealer lots, indoor | Unpowered trailers, containers, gensets | Outdoor trailers, containers, yellow iron | Reefers, secure cargo, regulated transport | Mixed indoor/outdoor dwell, harsh exposure | Parcels, pallets, one-way shipments |
| Install | Plug into OBD-II port, ~60 s | Hardwired to power + J1939 bus | Wired, engineered in | Mount and go | Bolt-on flange, 4 corner holes | Mount, panel to sky | Mount + sensor wiring | Screws, magnets or straps | Peel and stick to the carton |
| Power source | Vehicle OBD-II port | Vehicle power, optional backup battery | Vehicle 9–32 VDC | Replaceable 9,000 mAh LiMnO2 | 5.9 Ah rechargeable + ext. power | 1.5 W solar + battery | 1.5 W solar + battery, 6–24 VDC | 1.8 W solar + 12,000 mAh, USB-C | 2,500 mAh rechargeable |
| Field life | Vehicle-powered | Vehicle-powered | Vehicle-powered | Up to 5 yr (4× daily) | Up to 4 yr (1× daily) | 5–7 years | 5–7 years | Up to 10 yr (1× daily) | Up to 110 days per charge |
| Vehicle data | Engine bus, diagnostics, AI | ||||||||
| Engine / CAN data | Yes — OBD-II / CAN | Yes — SAE J1939 | Yes — 2× CAN, J1939 | — | — | — | — | — | — |
| Fault codes (DTC) | Yes | Yes — J1939 | Yes | — | — | — | — | — | — |
| Wayne AI | Early access | Contact us | Standard | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
| Positioning | Location and connectivity | ||||||||
| GNSS | GPS, GLONASS, Galileo, BeiDou | Multi-GNSS, external antenna | Concurrent GPS, GLONASS, BeiDou, Galileo | 72-ch multi-GNSS | 5 constellations + SBAS, ±1.5 m | Multi-constellation | Multi-constellation | 5 constellations + SBAS | GPS, BDS, GLONASS, QZSS, <10 m |
| Indoor positioning | — | — | — | — | — | — | — | Wi-Fi scanning | — |
| Cellular | LTE | LTE Cat 1, external antenna | LTE Cat-1 (18 bands) + fallback | LTE Cat-M1 | LTE Cat-M1 / NB-IoT | Cat-M / NB-IoT | Cat-M / NB-IoT | LTE Cat.1 bis | 5G LTE Cat-M + NB-IoT |
| Satellite option | — | — | FC-501-SAT (Starlink) | — | — | — | — | — | — |
| Coverage zones | Zones 1 & 2 included | Zones 1 & 2 included | Zones 1 & 2 included | Zones 1 & 2 included | Zone 2 only (N. America release) | Zones 1 & 2 included | Zones 1 & 2 included | Zones 1 & 2 included | Zones 1 & 2 included |
| Sensing | On-board and external | ||||||||
| BLE sensor gateway | Yes — in-cabin Neo | WLAN / BLE on FC-202-W | BLE 4.1 | — | BLE 5.3 | — | Wired I/O instead | BLE 5.4 | — |
| Temperature | Via Neo sensors | — | Via Neo sensors | — | Via Neo sensors | — | Wired probe | Via Neo sensors | On-board (Opening-Detection) |
| Door / tamper | Via Sentry-1 | — | Collision detection | — | Tamper + light sensor | — | Door open/close | Light-based tamper | Opening detection |
| Motion | Driver scoring | J1939 vehicle data | Collision detection | 3-axis IMU | 6-axis IMU | 6-axis IMU | 6-axis IMU | 6-axis + gyroscope | 3-axis accelerometer |
| Physical | Enclosure and environment | ||||||||
| Ingress rating | In-cabin | IP67 · J1455 | IP67 · J1455 | IP66 / IP67 | IP67 | IP67 crush-rated | IP67 crush-rated | IP68 | IP67 |
| Operating range | In-cabin | −30 to +70 °C | −30 to +70 °C | −20 to +60 °C | −10 to +60 °C | −20 to +70 °C | −20 to +70 °C | −20 to +80 °C | −20 to +60 °C |
| Weight | Plug-in dongle | Compact sealed unit | 170 g | 200 g | 194 g | 530 g | 540 g | 540 g | 47–58 g |
| Commercial | Hardware and plans | ||||||||
| Hardware | $53.00 | Contact sales | SDK Kit $500 | $64.00 | $77.00 | $165.00 | $197.00 | $125.00 | Contact sales |
| Plans | Track $13.99 · Command $18.99 | Locate $7.99 · Command $11.99 | Dev Seat $75/mo → Production | Locate $7.99 · Command $11.99 | Locate $7.99 · Command $11.99 | Locate $7.99 · Command $11.99 | Locate $7.99 · Command $11.99 | Locate $7.99 · Command $11.99 | Contact sales |
| Detail page | FC-201 → | FC-202 → | FC-501 → | FC-101 → | FC-103 → | FC-101S → | FC-101S-EX → | FC-101S-PRO → | FC102C → |
| Every plan includes the iMatrix EdgeUplink eSIM — 700+ networks in 190+ countries, best available network per country, no SIM swap at a border. Zones 1 (Europe) and 2 (North America and more) are included by default; Zones 3, 4, 5 and Verizon USA are available on request. You own the hardware outright on every SKU, month to month, with no multi-year term. | |||||||||
← Drag the blue bar under the table, or hold Shift and scroll, to reach every device → The spec column stays pinned as you go.
Tell us what the fleet looks like — how many powered vehicles, how many unpowered assets, and what you need to know about each — and we will map hardware to it. Most fleets end up with two SKUs, not one.