| ... | @@ -30,23 +30,5 @@ Each packet consists of two sections |
... | @@ -30,23 +30,5 @@ Each packet consists of two sections |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Header
|
|
|
|
|
## Required information
|
|
|
|
|
* protocol version (2 byte?)
|
|
|
|
|
* message type (2 bytes?)
|
|
|
|
|
* data from device
|
|
|
|
|
* data from controller
|
|
|
|
|
* metadata/housekeeping data from device
|
|
|
|
|
* metadata/housekeeping data from controller
|
|
|
|
|
* announcement (new device or component online) (or use different port?)
|
|
|
|
|
* command for device
|
|
|
|
|
* command for controller
|
|
|
|
|
* error from device
|
|
|
|
|
* error from controller
|
|
|
|
|
* network information command
|
|
|
|
|
|
|
|
|
|
* time stamp of sending (x bytes, format?)
|
|
|
|
|
*
|
|
|
|
|
|
|
|
|
|
# Open questions:
|
|
# Open questions:
|
|
|
- message length limitation: The maximum safe [UDP payload is 508 bytes](https://stackoverflow.com/a/35697810), is this enough for our purposes or do we need to worry about fragmentation? |
|
- message length limitation: The maximum safe [UDP payload is 508 bytes](https://stackoverflow.com/a/35697810), is this enough for our purposes or do we need to worry about fragmentation? |
|
\ No newline at end of file |
|
|
