Merge pull request #164 from andredunford/usb_docs

correction to usb device PID reference
This commit is contained in:
jankae 2022-11-27 09:29:05 +01:00 committed by GitHub
commit 8531d399f3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -168,7 +168,7 @@
\clearpage \clearpage
\section{USB device} \section{USB device}
The LibreVNA implements a ``custom class'' USB device. It uses a VID of 0x0483 and a PID of 0x4142. The custom class contains a single interface with three bulk endpoints: The LibreVNA implements a ``custom class'' USB device. It uses a VID of 0x0483 and a PID of 0x4121. The custom class contains a single interface with three bulk endpoints:
\begin{itemize} \begin{itemize}
\item \textbf{Endpoint 0x01:} Communication data from the USB host to the LibreVNA \item \textbf{Endpoint 0x01:} Communication data from the USB host to the LibreVNA
\item \textbf{Endpoint 0x81:} Communication data from the LibreVNA to the USB host \item \textbf{Endpoint 0x81:} Communication data from the LibreVNA to the USB host
@ -1010,4 +1010,4 @@ This packet is used when multiple devices are synchronized over USB and can be t
\subsection{ClearTrigger} \subsection{ClearTrigger}
This packet is used when multiple devices are synchronized over USB and can be transmitted in both directions. It has no payload. Synchronized devices must be logically organized in a closed loop. When a ClearTrigger packet is received from any devices in the loop it must be passed on to the next device in the loop. This packet is used when multiple devices are synchronized over USB and can be transmitted in both directions. It has no payload. Synchronized devices must be logically organized in a closed loop. When a ClearTrigger packet is received from any devices in the loop it must be passed on to the next device in the loop.
\end{document} \end{document}