M17_Project
/
M17_spec
mirror of https://github.com/M17-Project/M17_spec.git
1
0
Fork 0
Code Issues Releases Wiki Activity

3.0.0 draft update 

- added TLE packet type and its definition
- fixed callsigns
- updated changelist and fixed its formatting
pull/173/head
Wojciech Kaczmarski 2025-11-16 16:28:49 +01:00
parent 5c6322f03c
commit 75bcbd9f6c
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
M17_spec.tex
View File

@ -102,18 +102,18 @@ draw=black]
\renewcommand{\vhversionname}{Rev}
\renewcommand \vhAuthorColWidth{.3\hsize}
\renewcommand \vhChangeColWidth{1.7\hsize}
\vhEntry{1.0.0}{08 Dec 2019}{SP5WWP|N6MTS}{Formal specification repository created.}
\vhEntry{1.0.0}{08 Dec 2019}{SP5WWP|KR6ZY}{Formal specification repository created.}
\vhEntry{1.1.0}{25 Jan 2021}{KC1AWV}{Initial \LaTeX conversion from Sphinx.}
\vhEntry{1.2.0}{09 Sep 2024}{N7TAE|SP5WWP}{Removed Definitions and Control Packets sections, rewrote Callsign Encoding appendix using examples in C.}
\vhEntry{1.2.0}{09 Sep 2024}{N7TAE|SP5WWP}{Removed Definitions and Control Packets sections.{\newline}Rewrote Callsign Encoding appendix using examples in C.}
\vhEntry{1.3.0}{17 Oct 2024}{N7TAE|SP5WWP}{Introduced new LSD data type to clarify and correct discussion around LICH, and LSF.}
\vhEntry{1.4.0}{01 Jan 2025}{SP5WWP}{Removed the KISS appendix and created a separate KISS specification document.}
\vhEntry{1.5.0}{11 Feb 2025}{N7TAE|VK7XT}{Rearranged the Data Link and Application Layer chapters for better flow, removed IP Network chapter and File Type appendix, added more details to Packet Mode, 3 new IP packets defined, and added new clarifying bit tables.}
\vhEntry{1.5.0}{11 Feb 2025}{N7TAE|VK7XT}{Rearranged the Data Link and Application Layer chapters for better flow, removed IP Network chapter and File Type appendix.{\newline}Added more details to Packet Mode.{\newline}3 new IP packets defined.{\newline}Added new clarifying bit tables.}
\vhEntry{1.6.0}{08 Aug 2025}{SP5WWP}{Section 3.4 was moved to Part II.}
\vhEntry{2.0.0}{12 Aug 2025}{N7TAE|N1ADJ|SP5WWP}{GNSS Meta data changed extensively. Values are now metric, and a new param related to HDOP was added.}
\vhEntry{2.0.1}{23 Sep 2025}{K6OF}{Implement CCSDS A20.0-Y-4 style guide and clarify use of UTC.}
\vhEntry{2.0.2}{28 Sep 2025}{K0RET}{Fixed misspellings.}
\vhEntry{2.0.3}{09 Oct 2025}{SP5WWP}{Fixed Golay matrices display.}
\vhEntry{3.0.0-draft}{14 Oct 2025}{SP5WWP|IU2KWO|N1ADJ|N7TAE|LWVMOBILE}{Changed META text message padding (add more changes here).}
\vhEntry{3.0.0-draft}{16 Nov 2025}{SP5WWP|IU2KWO|N1ADJ|N7TAE|LWVMOBILE}{Redefined the TYPE field contents.{\newline}Changed META text message padding.{\newline}Changed how text data is sent using the META field.{\newline}Added TLE data packet type.}
\end{versionhistory}
\chapter{Licenses}
@ -1288,18 +1288,23 @@ The data type specifier can also be used as a protocol specifier. Table~\ref{tab
\texttt{0x04} & IPv4 \\
\texttt{0x05} & SMS (null-terminated, UTF-8 encoded string) \\
\texttt{0x06} & Winlink \\
\texttt{0x07} & TLE \\
\hline[2px]
\end{tblr}
\caption{Reserved Packet Protocol Identifiers}
\label{tab:reserved_packet_protocols}
\end{table}
The data type specifier is used to compute the CRC, along with the payload. Only format for SMS, \texttt{0x05}, has been specified.
The data type specifier is used to compute the CRC, along with the payload. Only format for SMS and TLE have been specified.
\subsection{SMS}
SMS is a way to send a null terminated UTF-8 text message quickly and efficiently. With a maximum of 33 data frames and 25 bytes per data frame, a 1-byte identifier, \texttt{0x05}, and a 2-byte CRC, the maximum number of characters in an SMS message sent via Packet Mode is $(33 \times 25) - 4$, or, $821$ bytes. The SMS message should not have any interspersed null bytes and should not contain any control characters expect for tab (\texttt{0x09}) and newline (\texttt{0x0A}). The CRC for the SMS type is inclusively calcuated from the identifier to the terminating null byte.
\subsection{TLE}
TLE data packet starts with the \texttt{0x07} 1-byte payload identifier. Actual TLE data should follow as ASCII text strings (all 3 rows), separated by newline characters (\texttt{0x0A}). After the last character of the last row, a null character is added, followed by a 2-byte CRC.
\appendix
\chapter{Address Encoding} \label{address_encoding}