Managing a tracker remotely requires knowing what the device reports, which command was sent, and how it responded. This update improved the Secure GPS map with digital output status, GPRS command notifications, and recent GPS movement direction. It also added response history, better organization by connection date, and a statistics correction for accounts with more than 100 devices.
Together, these functions provide more context to a control center: an operator can open a marker, review available signals, observe where the device was moving, follow an instruction as it is sent, and later review its delivery and response.
Digital output status from a map marker
Compatible trackers can report the state of their digital outputs. These outputs are device interfaces that, depending on model and installation, can be associated with accessories or external electrical actions.
When a user selects a marker on the map, Secure GPS displays the state reported by the device. This makes operational information available without leaving the location view and helps relate the state to the current position.
How digital output status helps
- Diagnostics: check the state reported by the tracker before investigating an installation.
- Context: bring device location and signals into the same view.
- Remote follow-up: compare status before and after an authorized action.
- Technical support: provide information for describing an exception to an installer or integrator.
The visible state represents data transmitted by the tracker. It does not by itself guarantee that a connected accessory reacted physically; verification depends on wiring, installation, equipment, and operational procedure.
Notifications when GPRS commands are sent and answered
Secure GPS added map notifications when a GPRS command is sent and when its response is received. GPRS is the mobile data channel used by many trackers to communicate with the platform, so this function lets users follow a remote action within the same supervision workflow.
The operator receives visual confirmation that the request was processed by the platform and can recognize when the device returned information. This reduces uncertainty for commands that previously required another area to check their status.
A device response does not always prove physical execution
Each status must be interpreted correctly. A sent command means the instruction left Secure GPS; a delivery date or response indicates communication according to available information. Actual execution can depend on protocol, coverage, power, configuration, installation, and vehicle or asset conditions.
For sensitive actions, teams should apply additional authorization and confirmation procedures. Commands that could affect a person's, vehicle's, or process's safety should not be executed without validating compatibility, operational condition, and manufacturer or installer recommendations.
Last five positions and movement direction
The movement trace view was renewed. In addition to the marker for the current location, the map can display a line connecting the last five positions visited by the device. Trace animation helps identify the recent direction of travel.
This short view is useful for quickly determining whether a device is approaching a point, moving away from an area, or maintaining a general direction. It does not replace full route history: it represents only the latest available positions and can be affected by reporting intervals or signal jumps.
Real-world uses of the recent trace
- Dispatch: estimate whether a vehicle continues toward the expected destination.
- Security: quickly detect a direction change that requires opening full history.
- Customer service: explain the recent movement of a delivery or service.
- Yard operations: recognize short movements between nearby points.
- Support: distinguish an isolated position from a coherent sequence of locations.
Command history with delivery and response
Response information for GPRS commands is retained for later review. On the device page, in the commands section, users can review the delivery date and response associated with instructions sent in the past.
This history helps reconstruct what was attempted, when communication occurred, and what the device answered. It supports technical assistance, operational audits, incident follow-up, and comparison of several attempts without relying on operator memory.
How to use command history responsibly
- Relate the command to the user and documented operational reason.
- Confirm date, time zone, device, and content before drawing conclusions.
- Interpret the response according to public documentation for the compatible protocol.
- Retain additional evidence when the action has safety or maintenance consequences.
- Limit command permissions to users who understand their effects.
Devices organized by connection date
Organization by connection date was optimized to make navigation between devices easier. This view helps locate devices according to communication freshness and prioritize equipment that requires follow-up.
A recent connection date indicates communication with the platform, but it does not necessarily mean movement or correct operation of every sensor. It should be combined with last position, status, alerts, and relevant data when evaluating a device.
Corrected statistics for accounts with more than 100 devices
This version corrected a statistics query issue that affected users with more than 100 devices. The improvement provides more complete and up-to-date statistical information for large operations, preventing device volume from improperly limiting results.
Values still depend on the period, permissions, transmission, and compatibility of each tracker. In a large fleet, teams should review samples, devices without data, and date ranges before treating the output as a final closeout.
Recommended workflow for a remote action
- Select the correct device and confirm its latest connection date.
- Review position, recent trace, and available digital states.
- Verify that the command is compatible and the user is authorized.
- Confirm that asset conditions allow the action to be executed safely.
- Send the command and monitor send and response notifications.
- Open the commands section to review delivery and response content.
- Use an additional method to confirm the physical result when required.
Functional summary for users and integrators
The update added digital output states to marker details; GPRS command send and response notifications; an animated trace connecting the latest five positions; retained delivery date and response information in command history; improved ordering by connection date; and corrected statistics for accounts with more than 100 devices. Each capability depends on the public protocol, reported data, installation, permissions, and tracker compatibility.
Explore Secure GPS plans and features to supervise GPS devices, analyze movement, and manage remote actions with greater context.