Teltonika FMC130 vs Rinho Spider IoT: CAN Bus and beyond
👉 Who this article is for: Integrators and fleet managers who need a tracker with CAN Bus and are evaluating whether to pay the additional cost of the Teltonika adapter or choose an alternative with native CAN.
⚠️ Disclaimer: This analysis reflects our perspective as Rinho manufacturers, but with a commitment to technical honesty. There's no perfect tracker for all cases — each project has different needs. Our philosophy is to help you choose the best for your specific case, even if that means recommending another brand.
Teltonika FMC130 is a popular tracker in the "Advanced" segment. But there's an important detail that many don't know: it doesn't have native CAN Bus.
Rinho Spider IoT competes in the same segment with native CAN integrated — without additional accessories.
Comparison Table
| Feature | Teltonika FMC130 | Rinho Spider IoT | Advantage |
|---|---|---|---|
| Cellular connectivity | LTE Cat 1 + 3G + 2G | LTE Cat 1 + 2G | FMC130 (3G) |
| WiFi | ❌ Not available | ✅ Integrated | Spider |
| BLE for sensors | BLE 4.0 | BLE 5.0 | Spider |
| GPIO | 3 In + 3 Out + 2 Analog | 4 DIN + 3 AIN + 3 DOUT | Spider |
| Native CAN Bus | ❌ Requires LV-CAN200 | ✅ Native (J1939, OBDII, IESCAN) | Spider |
| Event engine | 12 fixed scenarios | 196 programmable rules | Spider |
| Backup battery | 170 mAh | 500 mAh | Spider |
| Power supply | 10-30V DC | 8-38V DC | Spider |
| Protection | IP41 | IP30 (indoor installation) | Tie |
The CAN Bus myth in the FMC130
The FMC130 datasheet says "CAN Adapter inputs: 1". This does NOT mean it has integrated CAN.
To read CAN Bus data with the FMC130, you need to purchase separately the Teltonika LV-CAN200, an external adapter with significant additional cost.
Real cost of an FMC130 with CAN
| Component | Cost |
|---|---|
| FMC130 | Base price |
| LV-CAN200 (adapter) | Additional cost similar to tracker |
| Total | Nearly double the base price |
Spider IoT includes factory native CAN Bus, without external adapters, without hidden costs. It supports:
- SAE J1939 (trucks)
- OBDII (light vehicles)
- IESCAN (Mercedes-Benz)
CAN Bus: Profiles vs Flexibility
It's important to be transparent: Teltonika has years of accumulated reverse engineering with extensive databases of profiles by make/model/year. If your fleet uses common European brands with profiles already available, they have an advantage in initial setup time.
However, Rinho covers the main standards (OBDII, J1939, IESCAN) that cover most commercial fleets. And for proprietary parameters or vehicles without pre-configured profiles, CXECU allows defining custom CAN readings — something that with Teltonika requires waiting for them to add official support.
BLE Ecosystem: Integrated wireless sensors
Spider IoT includes factory BLE 5.0 — it's not an optional accessory. It allows connecting 4 fixed wireless sensors with detailed data, plus a BSW wildcard system that expands monitoring to dozens of sensors through smart grouping. Compatible with the Mokosmart line and other standard iBeacon/Eddystone manufacturers.
Immediate applications
| Sensor | Application |
|---|---|
| Rinho Condition (L02S) | Temperature, humidity, door opening, virtual trailer coupling |
| Rinho ID Band (W6) | Driver identification, start control, SOS button |
Success case: Virtual trailer coupling
Without cables or perforations in the fifth wheel, the system automatically detects which trailer is coupled to each tractor. When uncoupled outside an authorized geofence ? immediate alert. Read more about virtual coupling with Mokosmart.
The Rinho advantage
BLE data integrates with the 196 rules engine. You can create logic like:
IF BLE_door_sensor = OPEN
AND BLE_temperature > 8°C
AND vehicle_moving = YES
THEN → Critical alert + SMS + profile change
This is something Teltonika solves with limited predefined scenarios — not with complete programmable logic.
Need to integrate a specific sensor? Rinho's support team can adapt new BLE devices to your operation.
Event Engine: 12 vs 196
Same story as with the FMC920. FMC130 comes with 12 predefined scenarios that you can adjust but not extend.
Spider IoT has a 196 programmable rules engine with complete AND/OR/NOT logic, multiple conditions, and multiple actions per rule.
Example: Refrigeration alert combined with CAN
IF BLE_temperature > 8°C
AND compressor = OFF (via CAN J1939)
AND condition_time > 5 minutes
THEN
→ CRITICAL priority event
→ SMS to supervisor
→ Activate cabin buzzer
→ Change profile to "Emergency"
In FMC130: It's not possible to combine BLE sensors (which it doesn't have native) with CAN data (which requires an adapter) in automated logic.
In Spider IoT: One rule, all integrated.
WiFi: The unique differentiator
Spider IoT includes integrated WiFi. The FMC130 doesn't.
What is WiFi useful for?
- Starlink connectivity in rural areas
- Configuration without SIM from phone/laptop
- Bulk data download in depots without consuming mobile data
Total cost of ownership
| Concept | FMC130 + CAN | Spider IoT |
|---|---|---|
| Device | Base price | Inquire |
| CAN adapter | Additional cost | Included |
| Total hardware | ~Double base price | Inquire |
| Support | English, +6h timezone | Spanish, same timezone |
| WiFi | Not included | Included |
| BLE for sensors | Basic | 4 fixed + BSW expandable |
When NOT to choose Rinho Spider
For transparency, here are cases where Teltonika may be a better option:
| Situation | Why choose FMC130 |
|---|---|
| Need 3G | Spider is LTE Cat 1 + 2G, no 3G |
| Already have LV-CAN200 adapters | Leverage existing investment |
| Fleet 100% supported by Teltonika | Pre-configured CAN profiles |
| Already have Teltonika ecosystem | Maintaining operational consistency |
When to choose each one?
Choose Teltonika FMC130 if:
- You need 3G (Spider is LTE Cat 1 + 2G)
- You already have Teltonika infrastructure and the LV-CAN200 adapter
- Your fleet has CAN profiles already available in Teltonika
- You don't need WiFi or advanced BLE
Choose Rinho Spider IoT if:
- You need CAN Bus without buying additional adapters
- WiFi is critical for your operation (Starlink, depots)
- You want to integrate wireless BLE sensors
- You need automations beyond the 12 scenarios
- You value the lower total cost when CAN is required
Conclusion
FMC130 is a good device if you don't need CAN Bus. But if you do need it, the cost of the external LV-CAN200 adapter completely changes the economic equation.
Spider IoT offers native CAN + WiFi + BLE for sensors + 196 rules engine — features that the FMC130 simply doesn't have (or requires additional accessories).
Have a specific project and not sure which tracker to choose? Contact us and we'll help you evaluate the best option — even if it's not Rinho.