GPS tracking is more useful when the map reflects new positions quickly and sensors turn technical data into indicators that an operations team can understand. This Secure GPS update adds real-time map updates, support for a second fuel sensor, configurable formulas for analog sensors, new alert options, username recovery, and improved GPS device compatibility.
It also expands integration possibilities with an operation for retrieving alerts through the Secure GPS API.
GPS map updated in real time
Map locations now update in real time as Secure GPS receives new positions from devices. Users can keep the tracking view open and observe changes without manually refreshing the page for each update.
This function supports control centers, delivery operations, field service, and asset tracking. A coordinator can watch a vehicle advance, see that it is approaching a destination, or confirm that a tracker has resumed communication. The visible frequency depends on when the device obtains and transmits a position; “real time” does not mean Secure GPS can display data that the tracker has not yet sent.
Mute critical alerts without omitting them
The map can also silence critical alerts without omitting them. An operator can stop the audible interruption after beginning to handle an event while keeping the alert available for review. This reduces noise in a monitoring room without losing the reference to the event that requires attention.
Second fuel sensor with alerts and statistics
Secure GPS added support for a second fuel sensor on compatible devices. Its readings can be used in alerts and statistics, allowing customers to supervise two tanks, two measurement inputs, or another installation that requires separate signals, depending on the vehicle and tracker design.
- Review the behavior of each reading during a selected period.
- Create alerts associated with the second sensor when the transmitted data supports them.
- Compare changes and identify behavior that requires operational or technical investigation.
- Analyze fuel information alongside location, routes, and other device data.
Fuel readings depend on the sensor, installation, calibration, and quality of transmitted data. They should be treated as operational information and validated before attributing a change to consumption, refueling, draining, or a possible loss.
Formulas that convert analog sensors into fuel or temperature
Analog inputs from a compatible device can be mapped as fuel or temperature through a formula defined by the user in device settings. This function turns a technical signal into a unit that is meaningful to the operation.
For example, an integrator can relate an electrical reading to an estimated tank level or temperature when the scale and behavior of the installed sensor are known. The formula must be based on real measurements and device documentation. An incorrect conversion can produce misleading statistics or alerts, so teams should calibrate multiple points, compare results, and test the configuration before using it for critical decisions.
GPS alerts by email, SMS, and API
Text messages generated by alerts are now limited to 160 characters. This keeps the content within the standard size of an SMS and reduces fragmented messages. The notification should preserve the essential information needed to recognize the event, while Secure GPS provides additional context when the user opens the platform.
Authorized integrations gained the GetAlerts operation in the Secure GPS API. An external system can retrieve device alerts and use them in its own workflow, such as an operations dashboard, response process, or event consolidation. Integrations must follow current API documentation, authentication, permissions, and data scope.
More practical username recovery
User information can now include a mobile phone number to support account recovery. Secure GPS can also help users remember their username by using an associated device identifier or the phone number registered on the account.
This is useful when someone still has their tracker information or phone but cannot remember the username used to sign in. The data must match the applicable account and recovery process and does not replace other security checks.
Recognition of device identifiers
Secure GPS can automatically detect device identifiers entered with 14 characters and correct their verification digit. This assistance reduces registration errors when a tracker identifier needs its complete format to be recognized correctly.
Installers should always compare the result with the device label and documentation. A valid identifier is essential for associating incoming communications with the correct device in the customer's account.
Better Teltonika and Meiligao compatibility
This update corrected TCP communication for compatible Teltonika devices and millisecond calculations in messages from Meiligao equipment. These fixes improve message interpretation and the time consistency of information displayed by Secure GPS.
For customers, this means more dependable tracking when those protocols are used. For integrators, it reduces the need to compensate manually for behavior related to how each tracker transmitted its data.
Real-world application
A company operating vehicles with two tanks can connect compatible sensors, configure a calibrated formula for each signal, and review their statistics in Secure GPS. If a reading meets a configured condition, the team receives an alert; from the control center, an operator watches the vehicle on the real-time map and can silence the warning after beginning to address it.
The company can retrieve alerts through the API for an authorized dashboard and use Secure GPS history to investigate the event. When a technician registers a tracker with an incomplete identifier or works with Teltonika or Meiligao equipment, the corrections in this version help incorporate and process its data more consistently.
Technical summary for users and integrators
- Map locations update as new device positions are received.
- Critical map alerts can be muted without being omitted.
- A second fuel sensor is available for alerts and statistics on compatible equipment.
- Analog sensors can be mapped to fuel or temperature through configurable formulas.
- Alert SMS messages are limited to 160 characters.
- The GetAlerts API operation retrieves alerts for authorized integrations.
- Username recovery can use an account phone number or associated device identifier.
- Fourteen-character device identifiers are detected and their verification digit corrected.
- Compatibility fixes cover Teltonika communications and Meiligao message timing.
Secure GPS combines a GPS map, alerts, sensors, statistics, history, device management, and integrations so customers can supervise vehicles, people, and assets from one platform. Explore Secure GPS plans and features to review the capabilities currently available.