... | @@ -5,7 +5,7 @@ The microcontroller will do no any pre-processing of the data, but instead will |
... | @@ -5,7 +5,7 @@ The microcontroller will do no any pre-processing of the data, but instead will |
|
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.
|
|
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.
|
|
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
|
|
- each data packet must uniquely identify the source, hardware, and software versions
|
|
- sent time stamp?
|
|
- sent time stamp?
|
|
- message type code? E.g. data, error, device message, …
|
|
- message type code? E.g. data, error, device message, …
|
|
- a data header
|
|
- a data header
|
... | | ... | |