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
|
== Command-line Interface
Even though PulseView has a graphical user interface, there is also a command-line interface that
you can make use of. It is meant to provide functions for convenience and debug purposes, not to
replace the user interface itself.
Running
pulseview -h
gives you a list of these functions.
Since PulseView can't automatically scan for devices connected to a COM port (ttySx on Linux) or
Ethernet, you can tell it to look for a specific device using the -d or --driver parameter. Its
usage is the same as for sigrok-cli. For example:
pulseview -d lecroy-xstream:conn=vxi/192.168.178.20/111
Also, just as with sigrok-cli, you can specify -i / --input-file and -I / --input-format to open
a file on startup. Without -I, it is assumed that the file is in the native sigrok format (.sr).
You can also specify more than one file but they are all expected to be in the same format then.
Example:
pulseview -i data.csv -I csv:samplerate=3000000
If you previously saved a PulseView session setup alongside your input file, PulseView will
automatically load those settings so long as the setup file (.pvs) has the same base name
as your input file.
You can also manually specify a PulseView session setup file to load with -s / --settings.
Example:
pulseview -s settings.pvs data.sr
The remaining parameters are mostly for debug purposes:
-V / --version Shows the release version
-l / --loglevel Sets the libsigrok/libsigrokdecode log level (max is 5)
-D / --dont-scan Don't auto-scan for devices
-c / --clean Don't restore previous sessions on startup
Of these, -D / --dont-scan can be useful when PulseView gets stuck during the startup device scan.
No such scan will be performed then, allowing the program to start up but you'll have to scan for
your acquisition device(s) manually before you can use them.
Another potentially useful option is -c / --clean, which can be used when PulseView doesn't start
up and you don't know what could cause this.
Thus, the combination of both parameters can be seen as some kind of "safe mode" for PulseView:
pulseview -c -D
|
