This update expands Plaspy compatibility with GT06, QuecLink, Teltonika, Condor, GPS103, H02, Meiligao, TK103, and Gator trackers. The improvements focus on correctly interpreting locations, multiple events within one transmission, door and window sensors, new message types, and device responses. It also introduces visible behavior for distinguishing repeated identifiers on compatible connections.
More reliable GPS location and event interpretation
A GPS protocol defines how each part of a tracker message must be read. If a coordinate, event, or response is interpreted incorrectly, the map and route history can lose operational context. This release corrects several specific cases so Plaspy can turn compatible messages into more consistent information.
GT06: zero-value locations
GT06 message handling was corrected when the location contains a zero value. The goal is to prevent data without a usable position from being treated as a normal coordinate and affecting route interpretation.
Teltonika: event interpretation
Events sent by compatible Teltonika trackers are now interpreted correctly. This makes it easier to relate device messages to the status or event Plaspy presents to the user.
GPS103 and H02: multiple events in one transmission
GPS103 and H02 messages containing multiple events are now analyzed correctly. Plaspy can process the complete content instead of limiting interpretation to the first element, providing more context in device history.
New messages for QuecLink, Meiligao, and TK103
Hardware integrators need to know which message types the platform supports. This update adds the following public protocol contracts:
- QuecLink: support for binary message type
0x21. - Meiligao: support for event
0x5001. - TK103: support for event
BZ00.
These codes identify messages defined by their respective protocols. The information shown in Plaspy depends on the model, protocol version, and data actually transmitted by the tracker.
Door and window sensors on Condor devices
For compatible Condor trackers, the door input is assigned to sensor 2 and the window input to sensor 3. This mapping lets Plaspy distinguish both inputs and use them in supported display, history, and alert features.
In a real operation, a business can monitor whether a door or window changes state during a route. Before creating alerts, the technician should physically test each input and confirm that its change appears on the expected channel.
More consistent responses for Gator trackers
Responses to compatible Gator messages were corrected. This exchange is part of the communication between the tracker and Plaspy and helps the device manage data transmission according to its protocol.
Integrators can validate the improvement by confirming that the device maintains communications and continues sending locations after receiving the expected response.
Support for repeated GPS identifiers
Some trackers may share an identifier that is not unique across the platform. For a compatible connection method, Plaspy can add the :0 suffix to the received identifier to distinguish it from the original record.
This behavior should be treated as part of the device's public configuration. Administrators must register the identifier exactly as Plaspy recognizes it and use a test location to confirm that the message is assigned to the correct asset.
First stage of platform improvements
This release also begins the first of four stages in a broader update focused on security, stability, and performance. The work strengthens the foundation that receives device messages and supports tracking features without exposing internal technologies, architecture, or operational configuration.
Application in a real operation
A business integrating several models can connect a GT06 for basic location, a Condor with opening sensors, and a QuecLink with supported binary messages. Plaspy centralizes locations and events in the same environment while the integrator validates each protocol contract before delivering the project.
The advantage is a wider choice of hardware and fewer incomplete interpretations without requiring the operations team to use a different application for each brand.
Technical summary for integrators
- GT06 corrects handling for zero-value locations.
- QuecLink adds binary message type
0x21. - Teltonika corrects event interpretation.
- Condor assigns the door input to sensor 2 and the window input to sensor 3.
- GPS103 and H02 correct messages containing multiple events.
- Meiligao adds
0x5001and TK103 addsBZ00. - Gator corrects responses to compatible messages.
- A compatible connection method distinguishes repeated identifiers with the
:0suffix.
After any installation, integrators should validate the identifier, coordinates, time, sensors, events, and communication continuity. No event code should be used in a critical process without testing the corresponding model and protocol version.
Integrate trackers and sensors on one platform
Plaspy receives data from compatible GPS devices and turns it into maps, route history, events, sensors, and alerts. This update expands protocol coverage and improves the quality of information available to technicians and operators.
Explore Plaspy plans and features to review the capabilities currently available.
