This repository has been archived by the owner on Feb 28, 2019. It is now read-only.
forked from MichaelWallace30/CommProtocol
-
Notifications
You must be signed in to change notification settings - Fork 4
Request & Reply Packets
JasonZell edited this page Mar 2, 2018
·
2 revisions
The purpose of request/reply packet is to transmit data requests between vehicles. The request packet will be send from the requester to the receiver. The replay packet will be send from the receiver back to requester to confirm or deny the request.
Request packet schema
| Field | Size | Purpose |
|---|---|---|
| Requester Comm ID | uint_8 | Indicates sender's Comm ID |
| Receiver Comm ID | uint_8 | Indicates receiver's Comm ID |
| Data to be requested | uint_8 | Indicates what kind of data, User defined, 0x00 denote all available data |
| Control Flag | uint_8 | Indicate request to start transmit, Or stop transmission of said data. |
| Duration | uint_16 | Indicate data request duration, in seconds. 0x00 indicate infinite duration |
Reply packet schema
| Field | Size | Purpose |
|---|---|---|
| Replier Comm ID | uint_8 | Indicates replier's Comm ID |
| Receiver Comm ID | uint_8 | Indicates receiver's Comm ID |
| Data to be requested | uint_8 | Indicates what kind of data, User defined, 0x00 denote all available data |
| Control Flag | uint_8 | Control flag indicates acceptance or denial of said request. |
| Duration | uint_16 | Indicate data request duration, in seconds. 0x00 indicate infinite duration. Replier can override requester's duration request |