Skip to content
Snippets Groups Projects
Commit 2d531c29 authored by Stephen D's avatar Stephen D
Browse files

add balloon data to nodeinfo whisker

parent 9f68f8cc
No related branches found
No related tags found
1 merge request!2add balloon data to nodeinfo whisker
No preview for this file type
...@@ -763,8 +763,18 @@ Below is a table of variables. Each variable has an index, which indicates which ...@@ -763,8 +763,18 @@ Below is a table of variables. Each variable has an index, which indicates which
\hline \hline
8 & Battery Charge & 1 & u8 & $f(x) = 2.55x$ & percent \\ 8 & Battery Charge & 1 & u8 & $f(x) = 2.55x$ & percent \\
\hline \hline
9 & Altitude (See below) & 4 & f32 & $f(x)= x$ & meters \\
\hline
10 & Balloon (See below) & 0 & N/A & N/A & N/A \\
\hline
11 & External/ambient temperature & 1 & i8 & $f(x) = x$ & \degree C \\
\hline
\end{tabular} \end{tabular}
\textbf{Altitude}: Although the GPS whisker contains altitude already, it is only 2 bytes long. For most applications this is sufficient, but some require additional precision. For example, high altitude balloons need precise altitude information for accurate landing predictions. The NodeInfo whisker provides the ability to use a 4 byte float for altitude. If set, the NodeInfo whisker altitude should take precedence over the GPS whisker altitude. However, the GPS altitude should be set as close as possible to the NodeInfo altitude. This allows a system which does not implement the NodeInfo whisker to still have correct altitude information.
\textbf{Balloon}: If set, this packet was emitted by a high altitude balloon. Please only set this bit on an actual balloon payload. Transmitters incorrectly marked as balloons cause additional work, and complications, for downstream users of CATS. If, for some reason, you want a non-balloon to show up as a balloon, instead set the icon to be a balloon in the identification whisker, and leave the balloon bit clear.
\subsubsection{Bitmap} \subsubsection{Bitmap}
The NodeInfo whisker contains a 3-byte, or 24-bit, bitmap to keep track of which variables are actually used. The extra bits are intended to allow additional variables in the future. The MSB is assigned the index 23; the LSB is index 0. This corresponds to the variables in the above table. The NodeInfo whisker contains a 3-byte, or 24-bit, bitmap to keep track of which variables are actually used. The extra bits are intended to allow additional variables in the future. The MSB is assigned the index 23; the LSB is index 0. This corresponds to the variables in the above table.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment