.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.47.16.
.TH ISOTPSEND "1" "December 2020" "isotpsend 2020.11.0-1" "User Commands"
.SH NAME
isotpsend \- manual page for isotpsend 2020.11.0-1
.SH SYNOPSIS
.B isotpsend
[\fI\,options\/\fR] \fI\,<CAN interface>\/\fR
.SH OPTIONS
.TP
\fB\-s\fR <can_id>
(source can_id. Use 8 digits for extended IDs)
.TP
\fB\-d\fR <can_id>
(destination can_id. Use 8 digits for extended IDs)
.TP
\fB\-x\fR <addr>[:<rxaddr>]
(extended addressing / opt. separate rxaddr)
.TP
\fB\-p\fR [tx]:[rx]
(set and enable tx/rx padding bytes)
.TP
\fB\-P\fR <mode>
(check rx padding for (l)ength (c)ontent (a)ll)
.TP
\fB\-t\fR <time ns>
(frame transmit time (N_As) in nanosecs)
.TP
\fB\-f\fR <time ns>
(ignore FC and force local tx stmin value in nanosecs)
.TP
\fB\-D\fR <len>
(send a fixed PDU with len bytes \- no STDIN data)
.TP
\fB\-b\fR
(block until the PDU transmission is completed)
.TP
\fB\-L\fR <mtu>:<tx_dl>:<tx_flags>
(link layer options for CAN FD)
.PP
CAN IDs and addresses are given and expected in hexadecimal values.
The pdu data is expected on STDIN in space separated ASCII hex values.