TRIP Module

Advanced vehicle trip tracking system that captures and analyzes complete journey data.

What is it for?

Use case	Description
📊 Trip analysis	Captures complete metrics: distance, fuel, duration, efficiency
🎯 Drive Score	Configurable driving score (0-100)
📈 Histograms	Time distribution by RPM, speed, throttle and turbo ranges
👤 Identification	Driver code associated with each trip
🔢 GC Counters	8 generic counters for driving events
📍 Geolocation	Start and end GPS with 7-decimal precision

Technical Features

System Limits

Parameter	Range	Precision
Duration	0 - 455 hours (19 days)	1 minute
Distance	0 - 65,535 km	1 km
Fuel	0 - 6,553 liters	0.1 L
Efficiency	0 - 655.3 km/L	0.1 km/L
GPS	±180° lat/lon	7 decimals (~1cm)
Speed	0 - 255 km/h	1 km/h
RPM	0 - 10,000 RPM	10 RPM
Temperature	-40°C to 150°C	0.1°C
Driver code	1-16 characters	ASCII
GC Counters	0 - 65,535 events	1 event

Fuel Calculation Methods

The module automatically selects the best available method:

Method	Precision	Description
ODOLITER	±0.5%	Total odometer accumulator
FUEL_TRIP	±1%	ECU trip counter
CALCULATED	±5%	Calculation based on MAF/RPM
NONE	-	No data available

Trip Lifecycle

💤 IDLE

No active trip

STPSTART

🚗 ACTIVE

Trip in progress

STPSTOP

📊 IDLE

Data available

Typical Flow

Start trip: STPSTART or STPSTART,DRIVER_CODE
During trip: Automatic accumulation of GPS, CAN, sensor data
Query status: QTPSTATUS at any time
End trip: STPSTOP
Get reports: QTPR0, QTPR1, QTPSCO, histograms

Naming Convention

Prefix	Function	Examples
STP	Setters (modify state)	`STPSTART`, `STPSTOP`, `STPGCI,0`
QTP	Getters (query only)	`QTPSTATUS`, `QTPR0`, `QTPSCO`
RTP	Module responses	`RTPSTART`, `RTPSTATUS`

Response format:


>RTPCOMMAND,data;ID=<device_id>;*<checksum><

Scoring Counters (GC0-GC7)

Index	Name	Semantics	Use
GC0	OVERSPEED	Fixed	Speed violations
GC1	OVERREV	Fixed	RPM violations
GC2	HARSH_ACCEL	Fixed	Harsh accelerations (greater than 0.40g)
GC3	HARSH_BRAKE	Fixed	Harsh braking (less than -0.50g)
GC4	HARSH_CORNER	Fixed	Harsh cornering (greater than 0.50g)
GC5	CUSTOM_1	Client defined	E.g.: phone use, seatbelt
GC6	CUSTOM_2	Client defined	E.g.: fatigue, distractions
GC7	CUSTOM_3	Client defined	Custom events

Available Commands

🚗Trip Control

Start, stop and query trip status

→

📊Reports

Reports R0-R10 with complete trip data

→

🔢GC Counters

Generic event counters management

→

🎯Drive Score

Driving score configuration and query

→

📈Histograms

Time distribution by speed, RPM, throttle and turbo ranges

→

📉Global Statistics

Vehicle lifetime tachograph and odometer

→

⚙️Configuration

IDLE, NEUTRAL and scoring parameters

→

Quick Reference

Setters (STP)

Command	Description
`STPSTART`	Start trip
`STPSTART,<driver>`	Start trip with driver
`STPSTOP`	End trip
`STPDRV,<code>`	Set driver code
`STPGCI,<idx>`	Increment GC counter
`STPGCS,<idx>,<val>`	Set counter value
`STPGCE,<idx>,<0 or 1>`	Enable/disable counter
`STPSCOEN,<0 or 1>`	Enable/disable scoring
`STPSCOCFG,<params>`	Configure scoring weights
`STPIDLECFG,<t>,<rpm>`	Configure IDLE thresholds
`STPNEUCFG,<speed>`	Configure NEUTRAL speed
`STPNEUEN,<0 or 1>`	Enable NEUTRAL detection
`STPGRST`	Reset global statistics

Getters (QTP)

Command	Description
`QTPSTATUS`	Compact current status
`QTPR0`	Report part 1: GPS and metrics
`QTPR1`	Report part 2: speed, RPM, driver
`QTPR2`-`QTPR9`	Histograms
`QTPR10`	Complete Drive Score
`QTPDRV`	Driver code
`QTPGC,<idx>`	Query individual counter
`QTPGCL`	List of enabled counters
`QTPSCO`	Drive Score and analysis
`QTPSCOEN`	Scoring status
`QTPSCOCFG`	Weight configuration
`QTPRPM` / `QTPSPD` / `QTPTEMP`	Individual metrics
`QTPGTOT`	Complete global statistics
`QTPGREC`	Historical records
`QTPGSCO`	Global scores
`QTPGGC`	Accumulated counters
`QTPGKMS` / `QTPGTRIPS` / `QTPGHRS`	Quick queries

Integration with Other Modules

Behavior (HM)

HM events can increment GC counters:


// Configure HM00 for harsh GPS acceleration
>SHM00E,0,7,20,3,4000,10<
 
// Create rule to increment GC0 on harsh acceleration
>SRL20E;TRG=HM00+;ACC={STPGCI,0}<

Event Engine (RL)

Complete automation with rules:


// On trip start, send STATUS to server
>SRL04E;TRG=TD00+;ACC={GU401H}<
 
// On trip end, send complete report
>SRL00E;TRG=TD00-;ACC={GU000H}<

View Event Engine →

Basic Example


// 1. Start trip with driver
>STPSTART,JUAN123<
>RTPSTART,1; Trip started ...
 
// 2. Query status during trip
>QTPSTATUS<
>RTPSTATUS,active,1,45km,5.2L,1h15m,JUAN123...
 
// 3. End trip
>STPSTOP<
>RTPSTOP,1,45; Trip ended ...
 
// 4. Get drive score
>QTPSCO<
>RTPSCO,score:82,rating:GOOD,ovspd:3,ovrev:1,hacc:2,hbrk:4,hcrv:1,...

Troubleshooting

Problem	Cause	Solution
Score always 100	Scoring disabled	`>STPSCOEN,1<`
Counters don’t increment	Counters disabled	`>STPGCE,*,1<`
Fuel always 0.0L	ECU without fuel data	Check CAN connection
GPS +00000000+000000000	GPS without fix	Check GPS antenna
Empty histograms	Trip too short	Wait more time