Introduction
The GPS Transmission Activity report provides a detailed, packet-level view of device behavior and location reporting. When used with appropriate date ranges and proper interpretation of movement versus reporting, it is a powerful tool for understanding equipment activity and diagnosing potential issues.
Navigation
Fleet > Location > GPS Transmission Activity
What This Report Shows
Each row in the GPS Transmission Activity report represents a single message received from the device. These messages may reflect movement, engine state changes, transport activity, power events, or routine status updates.
A key point to understand:
A GPS transmission does not always mean the equipment is moving.
Devices report based on their configured ping rate and event triggers. Reviewing columns such as Latitude, Longitude, and Speed is essential to determine whether the equipment was actually moving or simply reporting while stationary.
Ping Rate
Ping Rate refers to how frequently a device reports data to FleetWatcher. Ping rates vary by device type and configuration and may include:
30 seconds
1 minute
5 minutes
12 hours
24 hours
Even when equipment is stationary, the device will continue to report at its configured interval. In these cases, you may see multiple rows with identical location and speed values.
Reason for Update
Reason for Update describes the event that triggered the transmission, such as engine activity, transport mode, battery events, or system updates.
This report uses the full, standard set of Reason for Update values. Detailed explanations for each reason are documented separately.
Placeholder: Link to Reason for Update definitions article
Helpful interpretation tips:
A device can send updates while the engine is running but the equipment is not moving.
Transport-related updates do not always indicate engine activity.
Reviewing Speed, Engine status, and location together provides the most accurate picture.
Report Filters and Date Behavior
Use the Report Filters to select the equipment and date you want to review.
If no date is selected, the report defaults to the last transmission day for that piece of equipment.
When using the default behavior, the report will display all transmissions from the first to last packet on that day.
Best Practice
For best performance, limit reports to 12–24 hours based on the device’s ping rate.
This report is data-heavy. Shorter date ranges improve performance and make the results easier to interpret.
Report Options and Actions
Column Selection
Checkboxes at the top of the report allow you to add or remove columns. All available columns are safe to toggle.
Commonly used fields are included in the default view. Additional fields such as
Battery Voltage or Satellite Count may be useful when diagnosing power or connectivity concerns.
Exporting the Report
Download CSV exports exactly what is shown on screen, including any added or removed columns.
Print PDF creates a printable version of the current report view.
Equipment and Map Tools
Click the Equipment Number to open the Equipment Details page.
Click Map to view the GPS location of a single transmission.
Click View Breadcrumb Trail to view an animated map showing each transmission in sequence for the selected time range.
Placeholder: Link to Breadcrumb Trail article
Understanding Map vs Breadcrumb Trail
Map button: Displays a static map view for a single transmission.
Breadcrumb Trail: Displays an animated sequence of all transmissions in the report range, allowing you to step through each ping over time.
Both views use the same timestamps and data shown in the report table.
Common Diagnostic Indicators
While this article does not replace formal troubleshooting workflows, the following items often warrant attention:
Transport Update: Indicates the device remains in transport mode.
Battery Disconnected: May indicate loss of equipment power or wiring issues.
Repeated pings with no change in location or speed may indicate stationary equipment.
Related diagnostic workflows are documented separately.
Placeholder: Link to device troubleshooting documentation