@@ -3,22 +3,28 @@ Scripts
33
44The following modules are callable from python-can.
55
6+ They can either be called by for example ``python -m can.logger `` or ``can_logger.py `` (if installed by pip).
7+ The scripts are internally placed in the module ``can.scripts.* ``,
8+ so they could also be launched by ``python -m can.scripts.logger ``.
9+
10+
611can.logger
712----------
813
9- Command line help (`` python -m can.logger -- help ``) ::
14+ Command line help, called with `` -- help ``::
1015
1116 usage: python -m can.logger [-h] [-f LOG_FILE] [-v] [-c CHANNEL]
12- [-i {iscan,slcan,virtual, socketcan_ctypes,usb2can,ixxat,socketcan_native, kvaser,neovi, vector,nican,pcan,serial,remote,socketcan }]
17+ [-i {pcan,ixxat, socketcan_ctypes,kvaser,virtual,usb2can, vector,slcan, nican,socketcan,iscan,neovi,serial,socketcan_native }]
1318 [--filter ...] [-b BITRATE]
19+ [--active | --passive]
1420
15- Log CAN traffic, printing messages to stdout or to a given file
21+ Log CAN traffic, printing messages to stdout or to a given file.
1622
1723 optional arguments:
1824 -h, --help show this help message and exit
1925 -f LOG_FILE, --file_name LOG_FILE
20- Path and base log filename, extension can be .txt,
21- .asc, .csv, .db, .npz
26+ Path and base log filename, for supported types see
27+ can.Logger.
2228 -v How much information do you want to see at the command
2329 line? You can add several of these e.g., -vv is DEBUG
2430 -c CHANNEL, --channel CHANNEL
@@ -27,7 +33,7 @@ Command line help (``python -m can.logger --help``)::
2733 might be a rfcomm device: "/dev/rfcomm0" With the
2834 socketcan interfaces valid channel examples include:
2935 "can0", "vcan0"
30- -i {iscan,slcan,virtual, socketcan_ctypes,usb2can,ixxat,socketcan_native, kvaser,neovi, vector,nican,pcan,serial,remote,socketcan }, --interface {iscan,slcan,virtual, socketcan_ctypes,usb2can,ixxat,socketcan_native, kvaser,neovi, vector,nican,pcan,serial,remote,socketcan }
36+ -i {pcan,ixxat, socketcan_ctypes,kvaser,virtual,usb2can, vector,slcan, nican,socketcan,iscan,neovi,serial,socketcan_native }, --interface {pcan,ixxat, socketcan_ctypes,kvaser,virtual,usb2can, vector,slcan, nican,socketcan,iscan,neovi,serial,socketcan_native }
3137 Specify the backend CAN interface to use. If left
3238 blank, fall back to reading from configuration files.
3339 --filter ... Comma separated filters can be specified for the given
@@ -37,29 +43,32 @@ Command line help (``python -m can.logger --help``)::
3743 mask != can_id & mask)
3844 -b BITRATE, --bitrate BITRATE
3945 Bitrate to use for the CAN bus.
46+ --active Start the bus as active, this is applied the default.
47+ --passive Start the bus as passive.
4048
4149
4250can.player
4351----------
4452
45- Command line help (`` python -m can.player -- help ``) ::
53+ Command line help, called with `` -- help ``::
4654
4755 usage: python -m can.player [-h] [-f LOG_FILE] [-v] [-c CHANNEL]
48- [-i {kvaser,virtual,slcan,nican,neovi,ixxat,serial, usb2can,socketcan_ctypes,remote,socketcan_native, iscan,vector,pcan,socketcan }]
49- [-b BITRATE] [--ignore-timestamps] [-g GAP]
50- [-s SKIP]
56+ [-i {pcan,ixxat,socketcan_ctypes,kvaser,virtual, usb2can,vector,slcan,nican,socketcan, iscan,neovi,serial,socketcan_native }]
57+ [-b BITRATE] [--ignore-timestamps]
58+ [-g GAP] [- s SKIP]
5159 input-file
5260
53- Replay CAN traffic
61+ Replay CAN traffic.
5462
5563 positional arguments:
56- input-file The file to replay. Supported types: .db, .blf
64+ input-file The file to replay. For supported types see
65+ can.LogReader.
5766
5867 optional arguments:
5968 -h, --help show this help message and exit
6069 -f LOG_FILE, --file_name LOG_FILE
61- Path and base log filename, extension can be .txt,
62- .asc, .csv, .db, .npz
70+ Path and base log filename, for supported types see
71+ can.LogReader.
6372 -v Also print can frames to stdout. You can add several
6473 of these to enable debugging
6574 -c CHANNEL, --channel CHANNEL
@@ -68,7 +77,7 @@ Command line help (``python -m can.player --help``)::
6877 might be a rfcomm device: "/dev/rfcomm0" With the
6978 socketcan interfaces valid channel examples include:
7079 "can0", "vcan0"
71- -i {kvaser,virtual,slcan,nican,neovi,ixxat,serial, usb2can,socketcan_ctypes,remote,socketcan_native, iscan,vector,pcan,socketcan }, --interface {kvaser,virtual,slcan,nican,neovi,ixxat,serial, usb2can,socketcan_ctypes,remote,socketcan_native, iscan,vector,pcan,socketcan }
80+ -i {pcan,ixxat,socketcan_ctypes,kvaser,virtual, usb2can,vector,slcan,nican,socketcan, iscan,neovi,serial,socketcan_native }, --interface {pcan,ixxat,socketcan_ctypes,kvaser,virtual, usb2can,vector,slcan,nican,socketcan, iscan,neovi,serial,socketcan_native }
7281 Specify the backend CAN interface to use. If left
7382 blank, fall back to reading from configuration files.
7483 -b BITRATE, --bitrate BITRATE
0 commit comments