Skip to main content

How to troubleshoot short or intermittent trips displayed on the server

At times, the trajectory of a vehicle or asset may appear interrupted or fragmented, creating gaps throughout trips. In the following article, we will analyze the possible causes and outline actions to diagnose the origin of these issues.

At times, the trajectory of a vehicle or asset may appear interrupted or fragmented, creating gaps throughout trips. This can lead to difficulties in traceability and result in data that may be considered unreliable or anomalous, directly impacting the desired metrics and monitoring.

Explanation:

Multiple short trips separated by only a few seconds or more are likely related to how the device determines ignition status. Stricter ignition detection conditions may delay recognition of actual vehicle movement, resulting in fragmented trip data. Event generation frequency can also vary depending on ignition status.

Additionally, issues with GSM or GNSS parameters may impact data generation or transmission. Factors such as distance, engine time, radial coefficients, and IO parameter configurations could also contribute. In some cases, the server itself may be incorrectly decoding the data.

Guidelines:

Recommended Troubleshooting Steps:

1. Validate GSM and GNSS Parameters:

  • Check GSM signal strength, cellular operator availability, and network technology

  • Confirm the number of available satellites and HDOP values

2. Review Ignition Configuration:

  • Verify ignition or custom ignition settings

  • Ensure the custom ignition IO parameter is configured to “on change” with High priority

3. Check GNSS Configuration:

  • Confirm GNSS settings are configured to use all available sources

4. Confirm Data Collection Frequencies

  • Review distance, time (with engine), and radial frequency settings

  • Compare these with server events

  • Use IO event data to identify which parameters generate each event

  • Refer to the FMIO List for detailed IO parameter descriptions: FMIO_List.xlsx

The following list contains common SMS commands used to check GSM status, GNSS availability, IO interfaces and power supply voltage:

<password> gsminfo

<password> coords

<password> getio

<password> info pwr

If no issues are identified through these steps, it will be necessary to double‑check the server side. If the data is being processed by a third‑party platform, the trip fragmentation may also be related to how that platform interprets and handles data from our devices.

Tools required:

Name:

Link:

SMS commands

FMIO List

Keywords:

Short trips, Intermittent trips, Ignition, GNSS, GSM, Custom ignition, Issues, Server, Third party server, Troubleshooting, SMS commands.

Automatically generated fields:

Document#

xxxxx

Created By:

Frank Grau

On:

04/05/2026 04:25:00

Modified By:

Name Surname

On:

dd/mm/yyyy hh:mm:ss

Did this answer your question?