|
|
|
We use UDP/IP as transport mechanism. All measurement data will be broadcast. This allows for redundant data acquisition and storage. Initially, we will not use encryption or authentication, which restricts us to physically isolated networks and physical security.
|
|
|
|
The microcontroller will do no any pre-processing of the data, but instead will only relay the data onto the network
|
|
|
|
|
|
|
|
**Requirements:**
|
|
|
|
Each packet should contain all necessary information to identify the both the hardware connected, but also the microcontroller hardware itself, and also the software version used. Furthermore, each packet should be self-contained and self-describing, i.e. not only the raw data, but also the description (e.g. a header) should be included.
|
|
|
|
Ideally data is sent as comma-separated list. This is the case for most (all?) CPCs and similar hardware.
|
|
|
|
|
|
|
|
- each packet must uniquely identify the source, hardware, and software versions
|
|
|
|
- sent time stamp?
|
|
|
|
- message type code? E.g. data, error, device message, …
|
|
|
|
- a data header
|
|
|
|
- the data itself, ideally in human readable format
|
|
|
|
-
|
|
|
|
**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? |
|
|
\ No newline at end of file |
