.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.47.4.
.TH J1939_LOGGER "1" "September 2016" "python-can" "User Commands"
.SH NAME
j1939_logger \- log J1939 traffic to the terminal and to a file on disk.
.SH DESCRIPTION
usage: j1939_logger [\-h] [\-v] [\-c CHANNEL] [\-i INTERFACE] ...
.PP
Log J1939 traffic, printing messages to stdout or to a given file.
.PP
The interface or channel can also be loaded from
a configuration file \- see the README for detail.
.SS "optional arguments:"
.TP
\fB\-h\fR, \fB\-\-help\fR
list all available options
.TP
\fB\-v\fR
command line verbosity
How much information do you want to see at the command line?
You can add several of these e.g., \fB\-vv\fR is DEBUG
.TP
\fB\-i\fR INTERFACE, \fB\-\-interface\fR INTERFACE
Specify the backend CAN interface to use (e.g. "socketcan")
.IP
Alternatively the CAN_INTERFACE environment variable can be set.
.TP
\fB\-c\fR CHANNEL, \fB\-\-channel\fR CHANNEL
Most backend interfaces require some sort of channel.
For example with the serial interface the channel might be a rfcomm device: "/dev/rfcomm0"
With the socketcan interfaces valid channel examples include: "can0", "vcan0".
.IP
Alternatively the CAN_CHANNEL environment variable can be set.
.SH SEE ALSO
can_logger(1)