A statistic is easier to investigate when it explains not only what happened and when, but also where. This Plaspy update adds latitude and longitude to alert, fuel, speed, and temperature records and lets users open the associated geographic point for further analysis.
The release also adds alerts that compare location attributes, improves alert editing, adds device search to the mobile map, supports file attachments when contacting Plaspy, and redesigns account modification. For integrators, it corrects Calamp sensor 1 detection and recognizes EElink activity messages.
Coordinates in alert, fuel, speed, and temperature statistics
Statistics tables now include the latitude and longitude corresponding to the record that produced each value. Coordinates are available in four areas:
- Alerts generated for the device.
- Fuel level readings or changes.
- Records used in speed statistics.
- Readings used in temperature statistics.
This connects a value with its geographic context. When an alert becomes active, speed reaches a certain level, or temperature changes, an operator can identify the associated point and open its map reference to investigate the area.
In a cold-chain operation, for example, a manager can review a temperature reading and identify the coordinates where it was recorded. In a fleet, the point related to an alert or fuel change can be compared with the vehicle's route.
The coordinates represent the position available for the record and depend on information sent by the tracker. They do not guarantee absolute physical accuracy by themselves because GPS signal, antenna placement, surroundings, and device configuration affect location.
Alerts that compare location attributes
Plaspy adds alert conditions that compare a location attribute with a defined value. Users can configure the rule to become active when the attribute is:
- Equal to the specified value.
- Less than the specified value.
- Greater than the specified value.
An attribute is additional data associated with a position beyond latitude and longitude. It may come from the tracker, a compatible sensor, or the interpretation available for that device. Specific choices depend on the attributes supplied by the equipment and its protocol.
This feature supports rules tailored to an operation. For example, a team can monitor whether a compatible value exceeds a limit or whether a numeric state matches an expected condition. Before using an alert for critical decisions, users should confirm how the tracker reports the attribute and test the rule with known data.
Alert editing with controls suited to each condition
The process for creating and modifying alerts was updated to present the data appropriate for each rule type. For attribute alerts, users can select an available attribute and define the required comparison and value instead of entering parameters without context.
Controls for other parameter types, such as dates or numeric values, were also organized accordingly. This reduces configuration errors and helps users understand the information an alert requires before saving it.
Filter devices on the mobile map
The mobile map adds search to filter the device list. By typing part of a name, users can reduce the visible results and find the phone, vehicle, asset, or tracker they need more quickly.
This is especially practical for accounts with several devices. A field coordinator can locate an item without scrolling through the entire list and then open its position on the map.
File attachments when contacting Plaspy
The Contact Us area lets users attach multiple files to a request, subject to the file types accepted by the platform. Messages can include material that helps explain the situation.
Screenshots, reference documents, or integration-related files can reduce additional exchanges and provide the support team with better context from the first message. Users should avoid including credentials, passwords, or other secrets that are not necessary to resolve the request.
Redesigned account modification interface
The screen used to update account information was reorganized to present its options more clearly. Users can identify available fields, review information before submitting it, and complete administrative changes with less confusion.
For a business, clearer account management helps when contact information or responsible-party details need to be updated. Available actions continue to depend on user permissions.
Corrected sensor 1 detection for Calamp trackers
Plaspy corrected sensor 1 detection in Calamp protocol messages. When a compatible device reports this input, the platform can represent its state consistently.
The sensor's meaning depends on the model, wiring, and installation configuration. It may be associated with different operational signals but must be verified for each device. The correction improves interpretation of received data; it does not add a physical input that the tracker has not configured.
Activity messages for EElink devices
EElink compatibility was expanded to recognize heartbeat or activity messages. These messages allow a tracker to maintain communication and report that it remains connected even when it does not need to send a complete movement event.
Correct interpretation helps distinguish a device activity signal from a new GPS position. For integrators and operators, this provides a more consistent view of communication status for compatible EElink trackers.
How this supports an operational investigation
Consider an attribute alert indicating a value above its configured limit. A manager can open statistics, review the record's latitude and longitude, and inspect the associated point. When working from a phone, the manager can filter the device name on the mobile map and access its location quickly.
If support is needed, screenshots or relevant documents can be attached to a request. At the same time, Calamp and EElink devices provide states interpreted according to their protocols. The update connects configuration, geographic context, mobility, and hardware compatibility.
Public technical summary
- Latitude and longitude in alert, fuel, speed, and temperature statistics.
- Map reference for investigating the point associated with a record.
- New attribute alerts with equal to, less than, and greater than comparisons.
- Alert creation and modification flow adapted to the parameter type.
- Search for filtering devices on the mobile map.
- Multiple file attachments in requests sent through Contact Us.
- Redesigned account modification interface.
- Corrected sensor 1 detection in Calamp messages.
- Recognition of activity messages from compatible EElink trackers.
