Repository navigation
Troubleshooting
Open Devices and check the selection. If the list is empty, have an administrator verify the Traccar connection under Settings → General, including API Base URL, credentials, and Device Source. Check the application's status message for connection errors.
Traccar Scope API login and the Traccar connection are separate, so a successful sign-in does not prove the tracker service is reachable.
Expand the appropriate year and month in Trips, then expand a day to see its trips. Use the refresh icon beside Trips. A month with a load error has a Retry action. Confirm that the intended devices are selected and that your account can access the corresponding vehicles. If history is still absent, have an administrator check stored data and device assignments.
On a wide screen, choose Reset windows to original positions from the map toolbar. This restores the default positions and hidden map keys. Panels can be dragged by their headings; Trips and Notifications have lower height-resize handles.
On a phone, use the bottom Map button to leave an expanded sheet, or the active task's Close button to return to navigation. Desktop floating positions do not control the compact sheet.
Check a numeric Data element. The initial graph may be empty until a field is selected. Confirm that the selected trip or days contain that field. Fields listed as ignored are not drawn.
If a graph does not open, check whether its day/trip graph button is available and whether the data is still loading. Close the active task before returning to Trips. Retain any error message when reporting a problem.
Check the point timestamp, field units, and assigned Device Protocol Profile. Verify the source key and conversion using a known sample. A graph can scale several fields together; review its normalization setting and field legend instead of interpreting every line directly from the vertical axis.
Read the point age and timestamp. Historical selections can show historical values. Some attributes are not present in every point, and available fields vary by tracker. Review Other fields and the status-card preferences inside Settings → Vehicle Catalog.
Verify Vehicle, From, Through, Tag, and report type, then choose Run report. Reports use the authorized saved-trip context; a loaded history summary and selected-trip detected events may not yet show identical counts. Refresh and compare the same time range and vehicle before treating a difference as missing data.
Review Current Device Assignments inside Vehicle Catalog and their effective dates. Avoid changing historical boundaries solely to bypass a conflict. Preserve the original file and status message for investigation.
Your account permissions, screen width, deployed version, tracker protocol, and installation settings affect the available controls. Regular-user Settings focus on personal preferences and alerts; shared setup requires an administrator and several configuration sections need a wider screen. The compact report/transfer menu opens Import/Export Data; the full report catalog uses Stats in the wide workspace.
The core Trips, mobile, map-control, Settings overview, report, graph, and field-selection captures were refreshed on October 22, 2026. Unchanged specialist configuration examples retain their earlier captures. Screenshots omit or cover identifying details and private locations.
Traccar Scope Help
- Home
- Getting started
- Mobile guide
- Automated Traccar + Traccar Scope installation
- Traccar Scope API
- Map and vehicle status
- Route point telemetry
- Trips, days, tags, and notes
- Telemetry graphs
- Reports
- Settings and vehicle setup
- Vehicle Catalog
- Named Places and track markers
- Trip Tags
- Device Protocol Profile Editor
- Import and export
- Troubleshooting