1 \section{General message format
}
2 Messages are delimited by newlines to make processing by line based devices
3 easier. Message exchanges have a
\emph{Request
} and
\emph{Response
} header.
4 The
\emph{Request
} header means that the server is sending to the client. The
5 \emph{Response
} header means that the client is sending to the server. In some
6 cases either the
\emph{Request
} or
\emph{Response
} is empty. This means that
7 the message is not acknowledged or responded upon. Multibyte values are
8 interpreted as
\gls{MSB
} first integers.
13 \begin{subfigure
}[t
]{.48\textwidth}
16 \multicolumn{2}{c
}{Request
}\\
21 \multicolumn{2}{c
}{Response
}\\
25 2 & Peripheral bitmask\\
26 3,
4 & Bytes of memory\\
27 5,
6 & Size of the stack\\
28 7 & Number of analog pins\\
29 8 & Number of digital pins\\
32 \caption{Send a device specification
}
40 \begin{subfigure
}[t
]{.48\textwidth}
43 \multicolumn{2}{c
}{Request
}\\
47 2,
3 & interval or interrupt\\
48 4,
5 & length (
\texttt{n
})\\
51 \multicolumn{2}{c
}{Response
}\\
58 \caption{Send a
\gls{Task
}}
61 \begin{subfigure
}[t
]{.48\textwidth}
64 \multicolumn{2}{c
}{Request
}\\
70 \multicolumn{2}{c
}{Response
}\\
77 \caption{Delete a
\gls{Task
}}
79 \caption{Message protocol for exchanging
\glspl{Task
}}
85 \begin{subfigure
}[t
]{.2\textwidth}
88 \multicolumn{2}{c
}{Request
}\\
95 \multicolumn{2}{c
}{Response
}\\
102 \caption{Send an SDS specification
}
105 \begin{subfigure
}[t
]{.2\textwidth}
108 \multicolumn{2}{c
}{Response
}\\
114 \multicolumn{2}{c
}{Request
}\\
121 \caption{Delete a SDS
}
124 \begin{subfigure
}[t
]{.2\textwidth}
127 \multicolumn{2}{c
}{Request
}\\
134 \multicolumn{2}{c
}{Response
}\\
140 \begin{subfigure
}[t
]{.2\textwidth}
143 \multicolumn{2}{c
}{Response
}\\
145 \multicolumn{2}{c
}{Request
}\\
153 \caption{SDS publish
}
155 \caption{Message protocol for exchanging SDSs
}