forked from ngscopeclient/scopehal-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsection-vna-drivers.tex
More file actions
89 lines (71 loc) · 2.85 KB
/
section-vna-drivers.tex
File metadata and controls
89 lines (71 loc) · 2.85 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
\chapter{VNA Drivers}
\label{sec:vna-drivers}
This chapter describes all of the available drivers for vector network analyzers.
\section{Copper Mountain}
\begin{tabularx}{16cm}{lllX}
\thickhline
\textbf{Device Family} & \textbf{Driver} & \textbf{Transport} & \textbf{Notes} \\
\thickhline
Planar & coppermt & lan & Not tested, but docs say same command set \\
\thinhline
S5xxx & coppermt & lan & Tested on S5180B \\
\thinhline
S7530 & coppermt & lan & Not tested, but docs say same command set \\
\thinhline
SC50xx & coppermt & lan & Not tested, but docs say same command set \\
\thinhline
C1xxx & coppermt & lan & Not tested, but docs say same command set \\
\thinhline
C2xxx & coppermt & lan & Not tested, but docs say same command set \\
\thinhline
C4xxx & coppermt & lan & Not tested, but docs say same command set \\
\thinhline
M5xxx & coppermt & lan & Not tested, but docs say same command set \\
\thickhline
\end{tabularx}
\subsection{coppermt}
This driver supports the S2VNA and S4VNA software from Copper Mountain.
As of this writing, only 2-port VNAs are supported. 4-port VNAs will probably work using only the first two ports,
but this has not been tested.
\section{NanoVNA}
\begin{tabularx}{16cm}{lllX}
\thickhline
\textbf{Device Family} & \textbf{Driver} & \textbf{Transport} & \textbf{Notes} \\
\thickhline
NanoVNA & nanovna & uart & Not tested but should work\\
\thinhline
NanoVNA-D & nanovna & uart & Not tested but should work\\
\thinhline
NanoVNA-F & nanovna & uart & Not tested but should work\\
\thinhline
DeepVNA 101 & nanovna & uart & Development and tests made on this device (a.k.a. NanoVNA-F Deepelec)\\
\thinhline
NanoVNA-F\_V2 & nanovna & uart & Not tested but should work\\
\thinhline
NanoVNA-H & nanovna & uart & Not tested but should work\\
\thinhline
NanoVNA-H4 & nanovna & uart & Not tested but should work\\
\thickhline
\end{tabularx}
\subsection{nanovna}
This driver supports the NanoVNA with different variants of the original design and firmware (see above).
Communication with the device uses UART transport layer with a connection string looking like this (DTR flag is required):
\begin{lstlisting}[language=sh, numbers=none]
COM6:115200:DTR
\end{lstlisting}
Paginated sweep has been implemented to achieve memory depths greater then the device's internal limit.
Pagination is also used at low RBW to prevent the connection from timing out during sweep.
NanoVNA V2 (with binary protocol) is NOT supported.
\section{Pico Technology}
\begin{tabularx}{16cm}{lllX}
\thickhline
\textbf{Device Family} & \textbf{Driver} & \textbf{Transport} & \textbf{Notes} \\
\thickhline
PicoVNA 106 & picovna & lan & \\
\thinhline
PicoVNA 108 & picovna & lan & \\
\thickhline
\end{tabularx}
\subsection{picovna}
This driver supports the PicoVNA 5 software from Pico Technology. The older PicoVNA 3 software does not provides a SCPI
interface and is not compatible with this driver.