Ruptela Protocol
TCP protocol published by Ruptela (Vilnius, Lithuania) for its Trace5, FM-Eco4, and Plug-and-Track families · the format Ruptela hardware uses to push positions, CAN bus data, and sensors to a fleet server.
On Traxelio
What Ruptela trackers do once they are on Traxelio
Geo-Zones
Get alerted when vehicles cross boundaries
Driving Behaviors
PremiumDriver scoring software to reduce accidents and insurance costs
Predictive Maintenance
PremiumAutomated maintenance scheduling that prevents breakdowns
Trip History
Every trip recorded, every dispute settled
Immobilizer request for compatible installations
Immobilizer requests for compatible installations
Fuel Level Monitoring
PremiumSee fuel level, volume, and consumption for every vehicle
Hardware that speaks this protocol
Devices that speak Ruptela
Point this protocol at Traxelio
Point Ruptela at Traxelio
-
1
Download Ruptela Configurator
Free Windows desktop tool from
doc.ruptela.lt. Works with any Ruptela-compatible server, not just TrustTrack. Trace5 + later firmware also accepts over-the-air configuration. -
2
Connect the device via USB or read OTA
USB connection for initial setup. For deployed fleets already reporting to a server, the configurator can read the device over GPRS.
-
3
Set the server endpoint
In the configurator's Server tab, set your platform's IP and port. Ruptela's default port is
5046but the device side is configurable · match your server's listener. Transport: TCP. -
4
Save and reboot
Click Save · the device reboots and reconnects. Confirm the first decoded position in Traxelio. CAN-bus calibration stays on the device through any server change.
-
5
Validate before cancelling the old server
Run one truck on the new server for a week to confirm positions + CAN data match what the previous platform showed. Then batch the rest of the fleet.
What Traxelio surfaces from these packets
Ruptela fields Traxelio reads
- GPS Location
- Speed
- Altitude
- Heading / Direction
- Street Address
- GPS Accuracy
- Ignition Status
- Odometer / Mileage
- Engine Hours
- Battery Level
- Fuel Level
- Network / Cell Info
Still offline after GPS lock
Ruptela still not landing
- Device reports to TrustTrack but stays silent after configurator change
Verify the configurator wrote the new server IP back to the device (Read configuration after Save to confirm). Power-cycle the tracker. If still silent, check the device's raw GPRS log for outbound TCP attempts · no attempts means SIM data session isn't active (APN, airtime, roaming block).
- Positions arrive but CAN bus channels are empty
CAN decoding is profile-driven · the device needs the right CAN profile loaded for the vehicle make/model (Mercedes Actros vs Volvo FH vs DAF XF use different FMS profiles). Use Ruptela Configurator's CAN profile selector or contact Ruptela support for the model code.
- Plug5 OBD-II tracker shows engine on/off correctly but no fuel level
OBD-II fuel level PID (0x2F) is optional · many European light vehicles do not expose it via the OBD-II port. For accurate fuel level on those vehicles, install an external capacitive or ultrasonic fuel sensor on RS232/RS485 rather than relying on OBD-II.
FAQ
Ruptela leftover questions
Is Ruptela FMTPv2 supported by Traxelio?
FMTPv1 (the current production protocol) is fully supported. FMTPv2 is a Ruptela-internal evolution not yet widely deployed in customer hardware as of 2026. When v2 ships to production fleets, Traxelio's ingest will be extended to decode it. Existing v1 devices keep working untouched.
Does Ruptela have a Lithuanian-only restriction?
No. Ruptela hardware is sold worldwide (150 countries per Ruptela's own marketing). The protocol itself is country-agnostic. In Senegal and West Africa, Ruptela devices route through European resellers · Traxelio sources authentic units and installs in Dakar (Ouest Foire).