UDP Machine Control Project
Protocol Message Format:
Ver + T + TKL + Code + MessageID + 11111111 + Command + Payload /c1>
01 + (00 | 01 | 02 | 03) + (000000)
The E0 4C 1E 5C 4C//dev->ser Device Login Request: message number: 0, ID is xx E0 4C1E,5C
The FF E0 4C 1E 5C 4C//ser->dev Server login response: message number: 0, the ID is xx E0 4C1E 5C 4C
E0 4C 1E 5C 4C//Dev->ser device Logout Request: message number: 1, id is xx E0 4C1E 5C 4C
The FF E0 4C 1E 5C 4C//Ser->dev Server Logout response: message number: 1, ID is xx E0 4C1E 5C /c13>
E0 4C 1E 5C 4C//Dev->ser device Heartbeat request: message No.: 2, ID is E0 4C1E,5C 4C
Server not responding in protocol
3, FF. E0 4C 1E 5C 4C//dev->ser device Data escalation request: message no .: /c7>
E0 4C 1E 5C 4C//ser->dev Server Data escalation response: message No.: 3, ID is E0 4C 1E, 5C 4c
The FF E0 4C 1E 5C 4C//dev->ser app control device request: message number: 4, ID is xx E0 4C 1E 5C 4C
E0 4C 1E 5C 4C//Ser->dev Device response App control: Message No.: 4, ID is E0 4C 1E/5C 4C
- The server side returns a response message ID that matches the message ID sent by the device
- Device ID using the MAC address form, the device's unique identifier
- Device login successful, return response; fail, no response; Exit for the same processing
- Heartbeat, 1 minutes hair once, 5 seconds did not receive your response, I will repeat the hair, 5 times in a row without your response, I will re-login
Exception (to be considered, what should be added to the exception to ensure the mechanism)
- After landing, in case the network is disconnected. For example, if your display device is already logged in, what will you do if I log in again?
Message data
40020000ff01000c0157a42ee900010203040500
[UDP] UDP Packet data (CoAP protocol)