Jump to content

List of Parameters: Difference between revisions

From Transight Wiki
No edit summary
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Binary Protocol Overview ==
== Binary Protocol Overview ==


This is a custom binary protocol designed for communication between device and a server. It is used in scenarios like vehicle tracking, remote diagnostics, OTA (Over-The-Air) updates, and device configuration. Each packet is structured with a defined header, payload, and checksum for integrity. The payload structure varies based on packet type and purpose.
This is a custom binary protocol designed for communication between device and a server. It is used in scenarios like vehicle tracking, remote diagnostics, OTA (Over The Air) updates, and device configuration. Each packet is structured with a defined header, payload, and checksum for integrity. The payload structure varies based on packet type and purpose.


=== Advantages of Binary Protocol ===
=== Advantages of Binary Protocol ===
* Compact (saves bandwidth)   
* Compact (saves bandwidth)   
* Faster to transmit and parse
* Faster to transmit and parse
* Suitable for constrained environments** like cellular networks (2G/4G)
* Suitable for constrained environments like cellular networks (2G/4G)


=== Comparison with Text Protocol ===
=== Comparison with Text Protocol ===
Line 14: Line 14:
== Packet Sending Modes ==
== Packet Sending Modes ==


Packet sending modes are based on the device data update rate source selected. The update rate is speed-based.
The vehicle’s mode is determined using a combination of location data from the GPS module, accelerometer data from the LIS2DE12 sensor (Measures force/vibration from vehicle movement), and the ignition state. These inputs are used to classify the vehicle's current mode into one of the following: Motion Mode, Halt Mode, or Sleep Mode.


The device can be in any of the following modes:
The device can be in any of the following modes:


=== Motion Mode (M) ===
=== Motion Mode (M) ===
If the speed of the vehicle is greater than 3 kmph, then the vehicle is in **motion mode**.
Motion Mode is activated when either of the following conditions is met:
* Linear Acceleration: The linear acceleration exceeds 0.5 m/s².
* Speed: The vehicle’s speed exceeds the threshold of 10 km/h.
Only one of these conditions needs to be satisfied for the system to enter Motion Mode. This indicates that the vehicle is in motion.


=== Halt Mode (H) ===
=== Halt Mode (H) ===
If the speed is less than 3 kmph and the duration in this condition is greater than CUHT, the vehicle enters halt mode.
Halt Mode is activated when both of the following conditions are satisfied:
* Linear Acceleration: The linear acceleration is below 0.3 m/s².
* Speed: The vehicle’s speed is below 10 km/h.
When both of these conditions are true, the system considers the vehicle to be stationary, hence entering Halt Mode.


=== Sleep Mode (S) ===
=== Sleep Mode (S) ===
If the vehicle remains in halt mode and the duration exceeds CUST, it enters sleep mode.
Sleep Mode is triggered when the ignition is switched off. As soon as the ignition state changes to off, the system immediately switches to Sleep Mode to conserve energy.


== Types of Packets & Packet Structure ==
== Types of Packets & Packet Structure ==
Discovery devices use a compact binary packet structure to transmit:
* Telemetry
* Alerts
* Device Info
* OTA commands
These packets are transmitted over networks using TCP or HTTP protocols.
Each packet contains:
* A defined header
* A payload
* A checksum for integrity
The payload structure varies based on the packet type and purpose.
== Types of Packets ==


* [[Device Info Packet]]
* [[Device Info Packet]]
* [[Telemetry Packet]]
* [[Telemetry Packet]]
* [[OTA (Over-The-Air) Packet]]
* [[OTA (Over-The-Air) Packet]]
* [[Error Packet]]
<!-- * [[Error Packet]] -->
* [[Device Configuration Packet]]
* [[Device Configuration Packet]]
* [[IP Configuration Packet]]
* [[IP Configuration Packet]]

Latest revision as of 05:12, 31 December 2025

Binary Protocol Overview

This is a custom binary protocol designed for communication between device and a server. It is used in scenarios like vehicle tracking, remote diagnostics, OTA (Over The Air) updates, and device configuration. Each packet is structured with a defined header, payload, and checksum for integrity. The payload structure varies based on packet type and purpose.

Advantages of Binary Protocol

  • Compact (saves bandwidth)
  • Faster to transmit and parse
  • Suitable for constrained environments like cellular networks (2G/4G)

Comparison with Text Protocol

  • No delimiters like commas, newlines, or JSON/XML formatting
  • Cannot be inspected or parsed in a terminal without a decoder

Packet Sending Modes

The vehicle’s mode is determined using a combination of location data from the GPS module, accelerometer data from the LIS2DE12 sensor (Measures force/vibration from vehicle movement), and the ignition state. These inputs are used to classify the vehicle's current mode into one of the following: Motion Mode, Halt Mode, or Sleep Mode.

The device can be in any of the following modes:

Motion Mode (M)

Motion Mode is activated when either of the following conditions is met:

  • Linear Acceleration: The linear acceleration exceeds 0.5 m/s².
  • Speed: The vehicle’s speed exceeds the threshold of 10 km/h.

Only one of these conditions needs to be satisfied for the system to enter Motion Mode. This indicates that the vehicle is in motion.

Halt Mode (H)

Halt Mode is activated when both of the following conditions are satisfied:

  • Linear Acceleration: The linear acceleration is below 0.3 m/s².
  • Speed: The vehicle’s speed is below 10 km/h.

When both of these conditions are true, the system considers the vehicle to be stationary, hence entering Halt Mode.

Sleep Mode (S)

Sleep Mode is triggered when the ignition is switched off. As soon as the ignition state changes to off, the system immediately switches to Sleep Mode to conserve energy.

Types of Packets & Packet Structure