Resources
Connecting a new device to an existing platform
Check the protocol, transmitted data, platform reception and what users can actually view
When a platform is already in use, describe its protocol requirements and the information the team needs. A shared protocol name is a starting point; data items, functions and configuration still need individual checks.
Match the model and protocol
Current documentation lists GT06 for Y18 and WYOBD, and JT808 for WY320. WY826 lists JT/T808-2013/2019, JT/T905 and JT/T1078. Keep the device model and documented version details in the integration request.
| Stage | What to confirm |
|---|---|
| Device transmission | Which data/events the chosen configuration sends, and the connection/reporting setup. |
| Platform reception | Whether the existing platform can receive and recognise the required records. |
| User access | Which information appears in the interface and which accounts can access it. |
Swipe horizontally to read the full table
Verify work tasks individually
For example, list location, ignition status and power-disconnection alerts as three separate requirements. If video, sensor data or remote commands are needed, add their hardware and software conditions. A device appearing in a list does not confirm every task.
Check one complete record
Choose a known device and a specific task. Compare the event time, the information produced, the platform record and the user-visible result. Record any difference with the configuration used. This suggested check helps define integration scope; it does not promise automatic or free integration.