Events Engine
Embedded automation system for telemetry
196 programmable rules to define logic like "when X happens, if Y is met, then do Z". No firmware compilation, no custom development, all configurable via commands.
Rule Structure
Complete conditional logic
TRIGGER
Defines what event starts the evaluation
CONDITION (Optional)
Additional filter that must be met
ACTION
What to execute when conditions are met
Why use the Events Engine?
Solve with configuration what previously required additional hardware or custom firmware development.
Cost Reduction
Eliminates external accessories like timers, relays, and logic modules. Everything in one device.
Total Flexibility
One firmware for multiple clients. Each installation adapts without custom development.
Operational Autonomy
Configuration changes without technical visits. Your clients can self-manage their rules.
Reliability
Local logic that doesn't depend on servers. Works even without internet connection.
Everything the module includes
A complete embedded automation system that transforms your GPS device into a programmable logic controller.
196 Simultaneous Rules
Massive programming capacity in a single device. Execute complex logic without limitations.
65+ Signal Types
GPS, CAN Bus, BLE sensors, digital inputs, accelerometer, and many more as triggers.
Remote Configuration
Modify rules via SMS or TCP from any platform, without technical visit.
No Custom Development
100% configurable logic with text commands. No firmware compilation required.
Local Execution
Rules run on the device. They work even without internet connection.
Flash Persistence
Rules survive power cuts and reboots. Stored in non-volatile memory.
65+ inputs for your rules
Each signal can be used as a trigger or as a condition. Combine multiple signals with logical operators to create complex rules.
Position and Movement
4 signal types
Vehicle
4 signal types
Wireless Sensors
4 signal types
System
4 signal types
Detail by Category
Position and Movement
- GPS status (valid fix, satellites, PDOP)
- Instant speed with thresholds
- 32 simultaneous geofences
- 3-axis accelerometer (braking/acceleration)
Vehicle
- Ignition (wire or voltage detection)
- CAN Bus: RPM, speed, fuel, temperature
- Hourmeter by ignition time
- 8 digital inputs, 8 control outputs
Wireless Sensors
- iBeacon and Eddystone (proximity)
- BLE fuel sensors (Escort, Technoton)
- BLE temperature and humidity sensors
- iButton for driver identification
System
- Cellular and WiFi connection status
- GSM jamming detection
- Pending data buffer
- Message delivery confirmation
What is it used for?
From transport fleets to vehicle security, the Events Engine solves use cases that previously required additional hardware.
Transport and Logistics
- Zone-differentiated speed control
- Off-route stop alerts
- Cargo temperature monitoring
- Door opening detection
Vehicle Security
- Fuel cut-off sequences
- GSM jamming detection
- Panic mode with recording
- Conditional geofences
Machinery and Equipment
- Maintenance alerts by hourmeter
- After-hours usage control
- Excessive idle monitoring
- Operator identification
This is how rules are configured
Each command defines complete logic. Let's see some typical cases.
Speed alert in specific zone
>SRL00E;TRG=VL00+;CND=WP05;ACC={GTX00L;@TRM;TXT=Exceso en zona escolar}<- Rule 00, enabled
- Triggers when speed exceeds limit
- Only if in geofence 5
- Sends alert to terminal
Panic button
>SRL01E;TRG=IN00+;ACC={GCQ99H;TXT=PANICO}{SSSXP011}<- Triggers with digital input 0
- Sends high priority alert
- Activates output 1 (siren)
Possible theft detection
>SRL02E;TRG=WP00-;CND=IGN!;ACC={GCQ00H;TXT=Vehiculo movido}<- Triggers when exiting geofence 0
- Only if ignition is off
- Sends urgent alert
Available on all devices
The Events Engine is integrated into the standard firmware of all our devices.
Frequently Asked Questions
Do I need to know how to program?
No. The rules use a predefined text syntax. It's more like configuring than programming, although it requires understanding the command structure.
Can I change the rules remotely?
Yes. Via SMS by sending the command directly, or via TCP from any platform that can send text to the device.
What happens if it loses connection?
The rules run locally. They don't depend on the internet. If there's an alert and no connection, it stays in buffer until it can be sent.
Can I use sensors from other brands?
We support standard iBeacon and Eddystone, plus specific profiles from Escort and MokoSmart. Other BLE sensors may require adding support.
Want to automate your fleet?
Contact us to learn how the Events Engine can simplify your installations and reduce operational costs.