@@ -452,7 +452,7 @@ The comment whisker specifies a textual comment on the CATS packet. The content
The route of a CATS packet is an ordered list of stations which have digipeated the packet. Each station consists of a callsign of arbitrary length, as well as a 1-byte SSID. The callsign must be valid UTF-8. This is identical to what is allowed in an identification whisker. \textbf{A valid CATS packet contains a maximum of one route whisker.}
Each callsign is represented as a set of bytes, which are valid UTF-8. After the last byte of the callsign should be a single byte of 0xFF, which acts as a delimiter. The next byte is the SSID for that callsign. Following that is the beginning of the next callsign. To represent a hop over the Internet, the byte 0xFE is used. This byte must be put where the start of a callsign is detected. The following byte will be used as the start of the callsign for the following hop. Multiple 0xFE bytes may be used in succession to represent multiple hops over the Internet.
Each callsign is represented as a set of bytes, which are valid UTF-8. After the last byte of the callsign should be a single byte of 0xFF, which acts as a delimiter. The next byte is the SSID for that callsign, proceeded by an RSSI byte. Following that is the beginning of the next callsign. To represent a hop over the Internet, the byte 0xFE is used. This byte must be put where the start of a callsign is detected. The following byte will be used as the start of the callsign for the following hop. Multiple 0xFE bytes may be used in succession to represent multiple hops over the Internet.
Instead of the 0xFF delimiter, 0xFD may be used. This signifies that the previous callsign is not part of the route yet. The first callsign in the route with a 0xFD delimiter must be the next digipeater. No other digipeaters should repeat the packet. A route may consist of a mixture of 0xFF and 0xFD delimiters, as long as there are no 0xFF delimiters after the first 0xFD delimiter.
...
...
@@ -462,6 +462,10 @@ The route whisker also contains a maximum amount of hops. This does not include
When digipeating, the callsign of the digipeater should be added to the route. The CATS packet should not be modified beyond this.
\subsubsection{RSSI}
Each node in the route has a byte that indicates the RSSI. This is the RSSI that the node received the packet at. For a given value $x$, representing the RSSI in dBm, the value encoded in the RSSI byte is $b =1.5x +240$. A value of 0 means the RSSI is not known. For example, if $x =-68$ dBm, then the encoded value in the route whisker would be $b =138$.
\subsubsection{Structure}
\begin{tabular}{|l|l|l|l|}
...
...
@@ -474,7 +478,7 @@ When digipeating, the callsign of the digipeater should be added to the route. T
\hline
2 & 1 && Maximum allowable digipeats \\
\hline
3 &$N -1$&& Callsigns and SSIDs \\
3 &$N -1$&& Callsigns, SSIDs, and RSSI values \\
\hline
\end{tabular}
...
...
@@ -484,11 +488,13 @@ When digipeating, the callsign of the digipeater should be added to the route. T
\hline
\textbf{Route}&\textbf{Max \# hops}&\textbf{Whisker Data (Hex)}&\textbf{Should digipeat?}\\