Will reloading the page create another GPS port?
No. A secure browser identity cookie reconnects the page to its existing active session, TCP port, countdown, and replayable event history. A different browser receives a different port.
Available
GPS Device Diagnostic
Start a browser-bound diagnostic session, configure an authorised GPS tracker with the temporary host and TCP port, and watch connection, framing, protocol identification, device identity, decoded telemetry, and acknowledgement events live. Reloading the page restores the same browser session and port until the fixed 15-minute expiry. Session logs are temporary and the tool does not write device data to the Open VTS database.
Tool Guide
Test a Real GPS Tracker on a Private Temporary TCP Port
The live GPS Device Diagnostic helps device integrators verify whether a tracker can connect, identify itself, produce complete protocol frames, decode useful telemetry, and receive a safe protocol acknowledgement. Each active browser receives one atomically bound TCP port for exactly 15 minutes, with reconnect-safe browser state and temporary session logging.
Common Use Cases
- Confirm that a cellular GPS tracker can reach your public diagnostic host and complete a TCP connection.
- Identify the tracker protocol, IMEI or device ID, packet type, and decoded telemetry from live device traffic.
- Inspect the exact acknowledgement bytes sent for certified GT06 and Teltonika packets without forwarding telemetry to production systems.
Key Features
- One private, conflict-free TCP port per browser session with automatic restoration after a page reload.
- A fixed 15-minute server-enforced lifetime, visible countdown, explicit End Session action, and automatic socket cleanup.
- Confidence-gated live detection across 269 synced protocol decoders, with certified ACKs limited to validated GT06 and Teltonika traffic.
- Ordered SSE event replay and temporary JSONL logs with no Prisma, PostgreSQL, or Redis telemetry writes.
Frequently Asked Questions
How long does a diagnostic session remain active?
Exactly 15 minutes from successful port binding. You can end it sooner with the End Session button. At expiry or manual ending, the listener and connected device sockets are closed server-side.
Does this tool save tracker data in the Open VTS database?
No. The diagnostic runtime has no database integration. It writes only a bounded temporary JSONL session log, which is deleted after download, after a short grace period, or when an abandoned browser session is cleaned up.
Does every detected protocol receive an acknowledgement?
No. Detection and decoding are available across the synced catalogue, but automatic acknowledgements are intentionally restricted to validated GT06 and Teltonika packets in this release. Ambiguous, failed, unidentified, or decode-only packets are never acknowledged automatically.
GPS device diagnosticGPS tracker TCP testlive GPS packet decoderGPS tracker listener testGT06 acknowledgement testTeltonika TCP testGPS IMEI diagnosticvehicle tracker protocol test